eapi | Edge API , building APIs | Key Value Database library

The provided output data does not list any data for the SecureEmployee property. So I'll assume your property hierarchy in your code is correct. The Value property contains an array of Employee objects that you will need to iterate.

When it comes to 0x80040154 REGDB_E_CLASSNOTREG and you are sure you registered COM server, the likely problem is 32/64 bitness mismatch.

Regardless of which regsvr32 you use, it would register in-process COM server with the bitness of the DLL.

IIS application pool has its own bitness setting and when the two mismatch your in-process COM server becomes unavailable.

Typical solutions are either build DLL for the other bitness and register respectively, or change IIS application pool bitness to reach the matching, see instructions here:

I finally got the code to work using jsSHA

As mentioned in CSRF token mismatch in post request in 3.6 version, the default app template lately has the CSRF protection middleware enabled by default, requiring CSRF tokens and cookies to be sent alongside non-GET requests.

You API should most likely require some form of authentication, and in case that authentication does not rely on cookies, or (HTTP) Basic authentication, or any other form of authentication which browsers/clients will automatically send/perform with HTTP requests, then you don't need CSRF protection, as CSRF would not be possible.

If you really don't need CSRF protection for your API, then you can disable it, for example by using a custom middleware handler that checks the request URL or route and applies the CSRF middleware conditionally, or by applying the middleware on routing scopes, so that you can exclude your API scope, see Cakephp 3.5.6 disable CSRF Middleware for controller.

If your API uses a form of authentication that is prone to CSRF, then you should figure out a way to serve the cookies (the middleware will automatically set the cookie on GET requests) and CSRF tokens (they are available on the request object like $request->getParam('_csrfToken')) to your clients, so that they can send them alongside their requests.

• Cookbook > Middleware > Cross Site Request Forgery (CSRF) Middleware
• https://security.stackexchange.com/questions/166724/should-i-use-csrf-protection-on-rest-api-endpoints

So if you check ionic doc example you will see that you need to pass data using json object and use its key to retrieve data, try this approach:

In your first component:

I think that you need to modify your eapi plug in to support your requirement.

For example, you can make a rule on your eapi plug to analysis the parameter's keyword.

1) if it is a simple string, return directly

2) if it is a string as similar as "{{{......}}}", use eval function to run it as a php script and then return.

If you are open to other APIs, let me suggest mesibo, it's much simpler to use,

If you just want the second part of the pipe delimited message then just return that part of the array, given you know the index...

This will output what you want