Cancel representation
Cancels the current representation process.
API Key authentication.
Format: Authorization: Bearer beel_sk_<key>
Scopes: API Keys use the same scopes as OAuth2 tokens. Each key is created with
specific scopes that limit which endpoints it can access. The required scope for each
endpoint is documented in the operation's security section under OAuth2.
Obtaining Keys: API Keys are managed from the BeeL dashboard
Security: API Keys are secret credentials. Do not share them or store them in source code
In: header
Path Parameters
uuidResponse Body
application/json
application/json
application/json
application/json
curl -X DELETE "https://app.beel.es/api/v1/companies/497f6eca-6276-4993-bfeb-53cbbbba6f08/representation/cancel"{
"success": true,
"data": {
"status": "string",
"message": "string"
},
"meta": {
"timestamp": "2025-01-15T10:30:00Z",
"request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}
}{
"success": false,
"error": {
"code": "UNAUTHORIZED",
"message": "Authentication required"
},
"meta": {
"timestamp": "2025-01-15T10:30:00Z",
"request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}
}{
"success": false,
"error": {
"code": "NOT_FOUND",
"message": "Resource not found"
},
"meta": {
"timestamp": "2025-01-15T10:30:00Z",
"request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}
}{
"success": false,
"error": {
"code": "INTERNAL_ERROR",
"message": "Internal server error"
},
"meta": {
"timestamp": "2025-01-15T10:30:00Z",
"request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}
}Validate NIF against AEAT registry POST
**Public endpoint** to validate a NIF/CIF against the AEAT registry using VeriFactu. This endpoint is useful for: - Pre-validation before registration (proactive feedback) - Validating customer NIFs before creating invoices - Verifying that a NIF exists in the registry **Behavior:** - **VALID**: The NIF exists in the AEAT registry. Returns the fiscal name. - **INVALID**: The NIF has correct format but doesn't exist in the registry. - **PENDING**: VeriFactu API is temporarily unavailable. The NIF has valid syntax but couldn't be verified against the registry. - **ERROR**: Technical error during validation (invalid syntax, timeout, etc.) **Note about PENDING:** If you use this endpoint for pre-validation during registration, a PENDING status indicates that the NIF has valid format and the user can continue. The system will validate the NIF automatically when the service becomes available. **Rate limiting:** - With API Key: 100 requests/hour - With Session Cookie: 1000 requests/hour **Authentication:** This endpoint accepts both API Keys and Session Cookies.
Create a company (sub-account) POST
Creates a new NIF/company under the authenticated account. Invoice series are created automatically with default values. The `environment` field decides the creation flow: * **`TEST`** — created immediately, free. `201` + `CompanyData`. * **`PROD` + owner already `PRODUCTION_ACTIVE`** (production activated, card on file) — created immediately as a production NIF (`environment=PROD`). Real emission stays blocked by `NIF_REPRESENTATION_REQUIRED` until the AEAT representation is signed for this `(owner, nif)`. The new NIF is added to the subscription (pay-as-you-go). `201` + `CompanyData`. * **`PROD` + owner `SANDBOX_ONLY`** — rejected with `400` `error.code=PRODUCTION_NOT_ACTIVATED`. Production must be activated for the account first — a one-time card capture done from the BeeL dashboard: switching to Live mode or creating the first production company there starts the activation checkout automatically. This activation is not part of the public API. Only once the owner is `PRODUCTION_ACTIVE` can a PROD NIF be created.