Remove the portal's cover photo
The portal's cover goes back to showing no photo; portal.cover stays as it was.
AuthorizationBearer <token>Your API key, which acts for the one business it was created for: fb_live_… keys work at api.fiscalbase.io and issue in live, and fb_sandbox_… keys work at api-sandbox.fiscalbase.io and issue in sandbox, on the simulated SRI. A key sent to the other host is refused with api_key_wrong_host, which names its host.
id*stringuuidFiscalbase-Environment?stringThe environment the call acts in. Required with a person's session; a key's own environment is the one that counts, so a key may leave it out, and naming another is 422 environment_mismatch.
"sandbox""test""live"Fiscalbase-Business?stringThe business the call acts for. With a person's session, the one the call is about (without it, a call about one business is 422 business_required and a list covers every business of the organization); a key acts for its own, so naming another is 422 business_mismatch.
uuidFiscalbase-Channel?stringWhich of Fiscalbase's own integrations a key's call comes from, recorded as the channel of the documents it issues: a record, not a permission. Without it, api. A person's call is always console.
"api""mcp"Fiscalbase-Agent?stringThe AI agent a key's call comes from, as its client names itself (the MCP server sets it); recorded with the request and shown in the console's request log.
Removed
curl -X DELETE 'https://api.fiscalbase.io/v1/ec/businesses/497f6eca-6276-4993-bfeb-53cbbbba6f08/portal-cover'Upload the portal's cover photo PUT
Replaces the previous photo. It is the cover of the portal's sign-in when `portal.cover` is `photo`. JPEG, PNG or WebP, up to 2 MB: the format is read from the file, not from its name. Needs Pro or A medida (`403` `portal_branding_plan_required`).
Issuing and its activation GET
Where a `live` business's issuing stands and what must be met before it is activated in `live`, with what to do in each case: a valid certificate, an emission point in `live` with its addresses, and an invoice authorized in `test`. It keeps its received documents in `live` whatever this says; only issuing waits for the activation, which a person makes from the console, and `business.issuing_updated` tells when the state or the lock moves. A `sandbox` business always issues: it answers `active`, `ready` with no checks.