This page differs depending on which API version you are browsing at the moment.
Service-secret headers are no longer supported. In V4, each Client is able to create an unlimited amount of API keys for API use. You can manage your keys on the Keys and Secrets page.
Each request will now have consistent auth headers:
Secret for both Apps and Services (ex: logins#create).
Attemptobject and from logins#create. Instead, the new
categorizationflag was added to the same route. Possible values:
md5 digestfrom imported file hash was changed to
sha1 digestfrom request signature was changed to
sha1 digestfrom callback signature was changed to
fetch_typewas replaced by
fetch_scopes, required on login/token create and is optional on login/token reconnect or refresh;
show_consent_confirmationis false. In other cases, it will be shown only when
identification_mode- provider attribute that shows whether the requests to the provider are made with your authorization headers or with SaltEdge’s;
identify_merchant- flag that shows if merchant identification is enabled for a login;
encrypted_credentialsthat can be sent on logins#create, logins#reconnect and logins#interactive;
consent_period_days- flag that allows limiting the time the consent is valid;
override_credentials_strategyflags that allow overriding previous credentials when reconnecting a Login via an API request or Token respectively;
Signature-key-versionwhich holds the version of the private key used to sign the callback. You can find the
public_keythat corresponds to this version here;
dynamic_select natures to provider fields;
immediate flag added to categories#learn route.
Provider logos (see
logo_url in provider attributes)
Secretdoes not exist or is
holder_info(Credit bureau for ex.) but sent