API V2: URL Base Migration

Migration Summary

The following guide is designed to help you migrate from the domain api.nodeflux.io to api.identifai.id.
If you are currently using api.nodeflux.io on the listed analytics below, you must now migrate to the api.identifai.id base URL.
  1. 1.
    Face Match
  2. 2.
    Face Liveness
  3. 3.
    Face Match Liveness
  4. 4.
    Face Match Enrollment
  5. 5.
    Create face enrolment (for supporting Face Match Enrollment)
  6. 6.
    Delete face enrollment (for supporting Face Match Enrollment)
  7. 7.
    OCR KTP
  8. 8.
    OCR SIM (beta)
  9. 9.
    OCR NPWP (beta)
  10. 10.
    Active-Passive Liveness SDK
Please migrate to the new endpoint by 31 January 2023, after that day the previous endpoint will be terminated.

Face Recognition Service Support

Face recognition service will be provided by Visionaire. There is no need to migrate to the new endpoint, and also applied for face recognition compliment features, such as face enrollment and delete enrollment, still use a similar endpoint. The usage will be counted and billed from Visionaire.
Due to the SKU separation, for the client who uses Face Recognition, you need to create a new access key dedicated for Face Recognition. The compliment analytics (create face enrollment and delete face enrollment) should be separated from Face Match Enrollment, too.
The API Usage & Invoice between IdentifAI and Visionaire will be separated on the system starting on 1 January 2023. For clients who use Face Recognition, you will get separate invoices.
If you have any difficulty during migration, please get in touch with our support team.

Migration Step

IdentifAI Base URL

IdentifAI API can be requested through HTTP(S) request with the base URL below:

Authorization

Generate New HMAC Token

The previous endpoint was https://backend.cloud.nodeflux.io/auth/signatures You need to generate a new access key and authorization key by sending a POST request to the endpoint https://api.identifai.id/public/auth/v1/signatures. The authorization method is still similar to the previous version. Read more about token authorization in our API reference.

Authorization Using Submission Token

If you use the submission token method, the previous endpoint was https://backend.cloud.nodeflux.io/auth/v2/submission_tokens , please migrate the endpoint to https://api.identifai.id/auth/v1/submission_tokens to generate the token for authorization.
Read more about submission token authorization in our Submission Token API reference.

Migrate to The New API Endpoint

Both asynchronous and synchronous API methods impacted these base URL changes. Yet, there are no changes to the payload request and structure. Check the list below for the new API endpoint changes.

Asynchronous API

Product/Service
Old Endpoint
New Endpoint
Face Match
https://api.cloud.nodeflux.io/v1/analytics/face-match
https://api.identifai.id/v1/analytics/face-match
Face Match Enrollment
https://api.cloud.nodeflux.io/v1/analytics/face-match-enrollment
https://api.identifai.id/v1/analytics/face-match-enrollment
Create Face Enrollment
https://api.cloud.nodeflux.io/v1/analytics/face-enrollment
https://api.identifai.id/v1/analytics/face-enrollment
Delete Face Enrollment
https://api.cloud.nodeflux.io/v1/analytics/delete-enrollment
https://api.identifai.id/v1/analytics/delete-enrollment
Face Liveness V4
https://api.cloud.nodeflux.io/v1/analytics/face-liveness-v4
https://api.identifai.id/v1/analytics/face-liveness-v4
Face Liveness V1
https://api.cloud.nodeflux.io/v1/analytics/face-liveness-v1
https://api.identifai.id/v1/analytics/face-liveness-v1
Face Match Liveness V2
https://api.cloud.nodeflux.io/v1/analytics/face-match-liveness-v2
https://api.identifai.id/v1/analytics/face-match-liveness-v2
Face Match Liveness V1
https://api.cloud.nodeflux.io/v1/analytics/face-match-liveness-v1
https://api.identifai.id/v1/analytics/face-match-liveness-v1
OCR KTP
https://api.cloud.nodeflux.io/v1/analytics/ocr-ktp
https://api.identifai.id/v1/analytics/ocr-ktp
OCR SIM
https://api.cloud.nodeflux.io/v1/analytics/ocr-sim
https://api.identifai.id/v1/analytics/ocr-sim
OCR NPWP
https://api.cloud.nodeflux.io/v1/analytics/ocr-npwp
https://api.identifai.id/v1/analytics/ocr-npwp

Synchronous API

Product/Service
Old Endpoint
New Endpoint
Face Match
https://api.cloud.nodeflux.io/syncv2/analytics/face-match
https://api.identifai.id/syncv2/analytics/face-match
Face Match Enrollment
https://api.cloud.nodeflux.io/syncv2/analytics/face-match-enrollment
https://api.identifai.id/syncv2/analytics/face-match-enrollment
Create Face Enrollment
https://api.cloud.nodeflux.io/syncv2/analytics/face-enrollment
https://api.identifai.id/syncv2/analytics/face-enrollment
Delete Face Enrollment
https://api.cloud.nodeflux.io/syncv2/analytics/delete-enrollment
https://api.identifai.id/syncv2/analytics/delete-enrollment
Face Liveness V4
https://api.cloud.nodeflux.io/syncv2/analytics/face-liveness-v4
https://api.identifai.id/syncv2/analytics/face-liveness-v4
Face Liveness V1
https://api.cloud.nodeflux.io/syncv2/analytics/face-liveness-v1
https://api.identifai.id/syncv2/analytics/face-liveness-v1
Face Match Liveness V2
https://api.cloud.nodeflux.io/syncv2/analytics/face-match-liveness-v2
https://api.identifai.id/syncv2/analytics/face-match-liveness-v2
Face Match Liveness V1
https://api.cloud.nodeflux.io/syncv2/analytics/face-match-liveness-v1
https://api.identifai.id/syncv2/analytics/face-match-liveness-v1
OCR KTP
https://api.cloud.nodeflux.io/syncv2/analytics/ocr-ktp
https://api.identifai.id/syncv2/analytics/ocr-ktp
OCR SIM
https://api.cloud.nodeflux.io/syncv2/analytics/ocr-sim
https://api.identifai.id/syncv2/analytics/ocr-sim
OCR NPWP
https://api.cloud.nodeflux.io/syncv2/analytics/ocr-npwp
https://api.identifai.id/syncv2/analytics/ocr-npwp

Get The Job Result

To get the API result on an asynchronous API method, the previous endpoint was https://api.cloud.nodeflux.io/v1/jobs/{job_id} you need to change the endpoint to https://api.identifai.id/v1/jobs/{job_id}.
We keep the API response similar to the previous one to keep the structure's compatibility.