Notabene IPs

If your firewall only lets known addresses through, allow the ones below. Traffic goes both ways: your systems call Notabene, and Notabene calls your webhook endpoint and reads your DID document.

Calls you make to Notabene

Host	Addresses
`https://sandbox.notabene.id`	The sandbox API. Still to be published.placeholder
https://eu-a.notabene.idplaceholder	The production API in the EU. Still to be published.placeholder
https://us-a.notabene.idplaceholder	The production API in the US. Still to be published.placeholder
`https://auth.notabene.id`	Where you request access tokens. Still to be published.placeholder

Host	Addresses
`https://sandbox.notabene.id`	The sandbox API. Still to be published. (placeholder)
https://eu-a.notabene.id (placeholder)	The production API in the EU. Still to be published. (placeholder)
https://us-a.notabene.id (placeholder)	The production API in the US. Still to be published. (placeholder)
`https://auth.notabene.id`	Where you request access tokens. Still to be published. (placeholder)

Authentication explains which base URL your institution uses.

Calls Notabene makes to you

What	Addresses
Webhooks	Deliveries to your endpoint come from Svix, which sends them for Notabene. Still to be published.placeholder
Your DID document	Notabene reads it over HTTPS from your domain. Counterparty institutions read it too, from their own addresses, so it must stay public. Still to be published.placeholder

What	Addresses
Webhooks	Deliveries to your endpoint come from Svix, which sends them for Notabene. Still to be published. (placeholder)
Your DID document	Notabene reads it over HTTPS from your domain. Counterparty institutions read it too, from their own addresses, so it must stay public. Still to be published. (placeholder)

You can check that a delivery comes from Notabene whatever its address, as described in Webhooks. For the DID document, Host your DID document explains where it lives on your domain.