Check the portal domain's DNS now
Looks up both DNS records now instead of waiting for the next scheduled check, which comes at most an hour later. Once both are found, the domain is registered at the edge right away; it turns active when its certificate is issued.
Your API key, which acts for the one business it was created for: fb_sandbox_… issues in sandbox, fb_test_… in test, the tax authority's testing service, and fb_live_… in live.
In: header
Path Parameters
uuidResponse Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X POST "https://example.com/v1/ec/entities/497f6eca-6276-4993-bfeb-53cbbbba6f08/portal-domain/verify"{ "object": "portal_domain", "entity_id": "8161163a-f227-466f-bc01-090a01e80165", "hostname": "string", "status": "pending", "portal_url": "http://example.com", "dns_records": [ { "type": "CNAME", "name": "string", "host": "string", "value": "string", "status": "found" } ], "failure_code": "dns_not_pointing", "failure_reason": "string", "last_checked_at": "2019-08-24T14:15:22Z", "verified_at": "2019-08-24T14:15:22Z"}Remove the custom portal domain DELETE
The portal stops answering on that domain right away and new links use `portal.fiscalbase.io/{entity_id}`; the registration with the edge provider is withdrawn afterwards. Links already sent to your customers with the custom domain stop working. To use it again, set it up again.
Who is calling GET
The environment the key issues in and what it may do, its organization, the business it acts for and that business's month. Ask it first.