canonical: https://jentic.com/apis/storecove.com/storecove

# Storecove API

Storecove API provides programmatic access to e commerce functionality. The API exposes 37 endpoints secured with apiKey authentication.

## For AI agents

Programmatically request a new c5 email activation, cancel a c5 email activation or deactivation. Covers 37 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Request a new C5 Email Activation
- Cancel a C5 email activation or deactivation
- DEPRECATED. Request a new C5 Activation
- Query and filter Storecove API records by parameters
- Monitor Storecove API operational status and events

## Use cases

### E-Commerce Operations

Use the Storecove API to perform e commerce operations programmatically. The API provides 37 endpoints covering core functionality including request a new c5 email activation, cancel a c5 email activation or deactivation, request a new c5 email deactivation.

Example prompt: Call POST `/api/v2/legal_entities/{legal_entity_id}/c5/iras/email/activate`(.{format}) to request a new c5 email activation

### Automated InvoiceSubmissions Management

Automate invoicesubmissions operations by combining multiple Storecove API endpoints. Agents can cancel a c5 email activation or deactivation and then request a new c5 email deactivation in a single workflow.

Example prompt: Call PUT `/api/v2/legal_entities/{legal_entity_id}/c5/iras/email/cancel`(.{format}) to cancel a c5 email activation or deactivation, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Storecove API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'request a new c5 email activation', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/v2/legal_entities/{legal_entity_id}/c5/iras/email/activate(.{format})` | Request a new C5 Email Activation |
| PUT | `/api/v2/legal_entities/{legal_entity_id}/c5/iras/email/cancel(.{format})` | Cancel a C5 email activation or deactivation |
| POST | `/api/v2/legal_entities/{legal_entity_id}/c5/iras/email/deactivate(.{format})` | Request a new C5 Email Deactivation |
| POST | `/api/v2/legal_entities/{legal_entity_id}/c5/iras/redirect/activate(.{format})` | Request a new C5 Redirect Activation |
| PUT | `/api/v2/legal_entities/{legal_entity_id}/c5/iras/redirect/cancel(.{format})` | Cancel a C5 redirect activation or deactivation |
| POST | `/api/v2/legal_entities/{legal_entity_id}/c5/iras/redirect/deactivate(.{format})` | Request a new C5 Redirect Deactivation |
| POST | `/api/v2/legal_entities/{legal_entity_id}/c5_activation/activate(.{format})` | DEPRECATED. Request a new C5 Activation |
| POST | `/api/v2/legal_entities/{legal_entity_id}/c5_deactivation/deactivate(.{format})` | DEPRECATED. Request a new C5 Deactivation |

## Key resources

- **InvoiceSubmissions** — Operations related to InvoiceSubmissions
- **DocumentSubmissions** — Operations related to DocumentSubmissions
- **LegalEntities** — Operations related to LegalEntities
- **PeppolIdentifiers** — Operations related to PeppolIdentifiers
- **Administrations** — Operations related to Administrations

## Why Jentic

- **Setup:** Wiring the Storecove API by hand means sending its API key in the Authorization header on every call to api.storecove.com/api/v2 and threading the legal-entity context through each invoice and document submission yourself. Through Jentic you install once, import the Storecove API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Storecove puts the legal entity id in the URL path (`/legal_entities/{legal_entity_id}/...`), so a rule can pin your agent to one legal entity: it can manage that entity's identifiers and submissions and nothing else. You choose the operations it may call, so deactivation and cancellation operations are not included unless you add them.
- **Credential handling:** Your Storecove API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'submit an invoice for a legal entity' or 'register a Peppol identifier', and Jentic returns the matching Storecove API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the Storecove API use?

The Storecove API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I request a new c5 email activation with the Storecove API?

Yes. Use the POST `/api/v2/legal_entities/{legal_entity_id}/c5/iras/email/activate`(.{format}) endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Storecove API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I request a new c5 email activation through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'request a new c5 email activation'. Jentic returns the matching Storecove API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Storecove API have?

The Storecove API exposes 37 endpoints covering invoicesubmissions, documentsubmissions, legalentities operations.

### Can I limit what my agent is allowed to do with the Storecove API?

Yes. Because you run Jentic One yourself, your own rules decide which Storecove operations and credentials the agent may use. Storecove carries the legal entity id in the URL path (`/legal_entities/{legal_entity_id}/...`), so you can pin the agent to a single legal entity and let it manage only that entity's invoice submissions, document submissions, and Peppol identifiers. You also pick the exact operations it may call, so the C5 deactivation and cancellation endpoints stay off limits unless you explicitly add them.