canonical: https://jentic.com/apis/swaggerhub.eco-solutions/agrocuracrm-pengeprofilen-api

# Eco Solutions AgrocuraCRM PengeProfilen API

API Documentation for PengeProfilen to integrate with Agrocura CRM. <br>For demo purposes please use customerId '5e9eaccff1ca663a888ea470'. The API exposes 2 endpoints secured with apiKey authentication.

## For AI agents

Programmatically creates pengeprofil activity, deletes customer pengeprofil reference. Covers 2 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for social media only.

## Capabilities

- creates pengeprofil activity
- deletes customer pengeprofil reference
- Integrate AgrocuraCRM PengeProfilen API into automated workflows
- Query and filter AgrocuraCRM PengeProfilen API records by parameters
- Monitor AgrocuraCRM PengeProfilen API operational status and events

## Use cases

### Social Media Operations

Use the AgrocuraCRM PengeProfilen API to perform social media operations programmatically. The API provides 2 endpoints covering core functionality including creates pengeprofil activity, deletes customer pengeprofil reference.

Example prompt: Call POST /customers/pengeprofilen/{customerId}/addActivity to creates pengeprofil activity

### Data Retrieval and Monitoring

Query AgrocuraCRM PengeProfilen API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary AgrocuraCRM PengeProfilen API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call AgrocuraCRM PengeProfilen 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 'creates pengeprofil activity', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /customers/pengeprofilen/{customerId}/addActivity | creates pengeprofil activity |
| DELETE | /customers/pengeprofilen/{customerId} | deletes customer pengeprofil reference |

## Key resources

- **Customer** — Operations related to Customer

## Why Jentic

- **Setup:** Wiring the AgrocuraCRM PengeProfilen API by hand means learning its x-api-key header auth, pointing at the crm.agrocura.dk host, and hand-coding each customer call and its retries yourself. Through Jentic you install once, import the AgrocuraCRM PengeProfilen API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The AgrocuraCRM PengeProfilen API puts the customer id in the URL path (/customers/pengeprofilen/{customerId}/...), so a rule can pin your agent to one customer: it can add an activity for that customer and nothing else. You choose the operations it may call, so destructive ones like deleting the customer are not included unless you add them.
- **Credential handling:** Your AgrocuraCRM PengeProfilen 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 'add an activity for a customer', and Jentic returns the matching AgrocuraCRM PengeProfilen API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Facebook** — Alternative social media API
- **Twitter** — Alternative social media API
- **Linkedin** — Complementary social media API

## FAQ

### What authentication does the AgrocuraCRM PengeProfilen API use?

The AgrocuraCRM PengeProfilen API uses an API key passed in the `x-api-key` 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 creates pengeprofil activity with the AgrocuraCRM PengeProfilen API?

Yes. Use the POST /customers/pengeprofilen/{customerId}/addActivity endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the AgrocuraCRM PengeProfilen 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 creates pengeprofil activity through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'creates pengeprofil activity'. Jentic returns the matching AgrocuraCRM PengeProfilen API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the AgrocuraCRM PengeProfilen API have?

The AgrocuraCRM PengeProfilen API exposes 2 endpoints covering customer operations.

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

Yes. Because Jentic One is self-hosted and you set its rules, you decide which of the two operations your agent may call: adding an activity with POST /customers/pengeprofilen/{customerId}/addActivity, deleting a customer reference with DELETE /customers/pengeprofilen/{customerId}, or only one of them. Since the customer id sits in the URL path, a rule can pin the agent to a single customerId so it acts on that customer and no other. This means you can allow activity creation while leaving out the destructive delete unless you explicitly grant it.