Try in playground

Chapter 04 of 05 · UAE sandbox

Submit the invoice

Send your prepared UAE invoice through Unify and save its tracking identifier. You need the sandbox API key and uae-invoice-request.json from the previous chapter.

Send the request

Submit the prepared invoicebash
curl --request POST 'https://prod.gets.complyance.io/api/v3/unify' \
  --header "Authorization: Bearer ${COMPLYANCE_API_KEY}" \
  --header 'Content-Type: application/json' \
  --header 'Accept: application/json' \
  --header 'new-api: true' \
  --data @uae-invoice-request.json \
  --output invoice-response.json

Use the request file you reviewed in the previous chapter. Unify uses the Bearer header, unlike Connect’s X-API-Key header.

Keep the response

Read invoice-response.json and save the returned documentId alongside your invoice number. Keep any request identifier and error information if the request fails.

A successful HTTP response means the submission request succeeded. Check the document’s final state before recording the invoice as accepted.

If something goes wrong

Authentication fails: check the Bearer header and sandbox key.

The source or mapping is rejected: compare the request’s source with the onboarding response and confirm readyForInvoicing.

The response is lost: check the portal for the original invoice before sending it again. Do not assume a timeout means nothing was submitted.

The next chapter checks the saved document identifier until a final result is available.

Last updated

05 Next: check the result Read the status and handle any errors.