If you’ve received a notification that you previously backgrounded transaction has completed, or you wish to re-retrive a result from an earlier transaction, then you can simply request the result from our encrypted cache
The response will return the original HTTP code, along with the payload that would have been returned in the original request. The data can be re-retrieved for a maximum of 3 days.
This will be the same RequestId that was sent in the 202 acceptance response.
Customer ID issued by Frankie Financial. This will never change. Your API key, which is mapped to this identity, will change over time.
If, as a Frankie Customer, you are acting on behalf of your own customers, then you can populate this field with a Frankie-assigned ID.
Note: If using a CustomerChildID, you will also need a separate api_key for each child.
Any documents, checks, entities that are created when this field has been populated will now be tied to this CustomerID + CustomerChildID combination. Just as Customers cannot see data created by other Customers, so too a Customer’s Children will not be able to see each other’s data.
A Customer can see the documents/entities and checks of all their Children.
Specifies the type of the payload field in the retrieved response. Default is ‘string’.
The request was valid and able to be processed in some fashion. Results may or may not be successful, but it was completed as far as practical with no actual errors.
This will be the HTTP response code that was returned originally (200, 404, etc).
In the case where you’re requesting the result of a callback (previously backgrounded call), then this is the response that would have been sent, had you waited for the call to finish.
This is a placeholder field. It will actually be a JSON object that is the payload that would have been returned (or was returned) in the original request. You’ll need to process this as if it were the original response, and act accordingly.