Build a request to the API.
Pick an operation and fill in its fields. The page writes the call in curl, fetch and the SDK, with your key as a variable and a fresh idempotency key. Nothing is sent from this page.
The call
curl -X POST 'https://api.eternifylabs.com/v1/bills' \
-H "Authorization: Bearer $ETERNIFY_API_KEY" \
-H 'Idempotency-Key: 00000000-0000-4000-8000-000000000000' \
-H 'Content-Type: application/json' \
-d '{
"entityId": "<entityId>",
"billDate": "<billDate>",
"lines": [
{
"description": "text",
"supplyCategory": "GOODS",
"itcKind": "GENERAL"
}
]
}'Still to fill in: entityId, billDate. Each prints as a name in angle brackets until you do.
Questions, answered.
Does the request builder send the request?
No. It writes the call as text from the published contract and makes no request. You run the code yourself, with your key in the ETERNIFY_API_KEY variable.
Where do I get a key?
An administrator on your books makes it in the app, under Connected apps. There is no developer sign-up. If your company is not a customer yet, book a demo.
What is the Idempotency-Key for?
A write carries a new value for each new request and the same value when you retry it, so a bill whose answer was lost is created once, not twice. The builder gives each call a fresh UUID, and the SDK sends one for you when you do not.
Why do some values print in angle brackets?
A required value you have not filled in prints as its name, such as <billId>, so the call still reads whole. Replace each one before you run it.
The reference lists every field and response, and the webhook signature checker checks the deliveries you receive.
Build on your books.
Customers' administrators make API keys in the app. Book a demo if your company is not a customer yet.