...
The following table provides the values for URL API host-name wildcards used in the documentationin testing and production environments.
Host-name wildcard | Testing environment | Production environment |
|---|---|---|
|
|
|
URL Namespace
All APIs are accessible over HTTPS, the base URL for all API requests is {{everifin_multibankingapi_url}}/api/{apiversion{{api_version}}
The apiversion api_version is currently v1.
Any values enclosed with double curly braces {{...}}, e.g. {{youreverifin_appapi_valueurl}}, should be replaced by values specific to your case, or specified in the documentation.
| Info |
|---|
All API requests must use HTTPS scheme, any non-secure (HTTP) requests return a (HTTP 301) redirect to a HTTPS equivalent of the original request URL. |
HTTP
...
request methods
As per RESTful design patterns, our API implements the following HTTP verbsrequest methods:
GET- used for retrieveing objectsPOST- Used for creating objectsPUT- Used for replacing objects or collectionsDELETE- Used for deleting objects
Parameters
Many API methods take parameters.
For
GET requests, any parameters not specified as a segment in the path can be passed as an HTTP query string parameter:
Media types
The API currently only supports JSON as an exchange format. Be sure to set both the Content-Type and Accept headers for every request as application/json.
...
User agent header should be present in all requests. This should be the User Agent of the actual end user (client of the bank) using your application, whenever possible.
IP address
client-ip-address header should be present in all requests. This should be the IP Address of the actual end user (client of the bank) using your application, whenever possible.
...
| Code Block |
|---|
{
"errors": [
{
"code": "DATA_NOT_FOUND",
"title": "Data not found.",
"detail": "Account CZ12080000000002594591015 not found in user profile."
}
],
"meta": {
"status": "ERROR"
}
} |
See Errors , and API Postman documentation with examples for a list of API error codes and more details.
...