aYOUne
translate
Not in your language

This page is not yet available in en. You're reading the de version.

Developer Portal Übersicht

Das aYOUne Developer Portal bündelt alles, was du brauchst, um die Plattform aus deinen eigenen Anwendungen heraus anzusprechen — von simplen REST-Calls über Webhooks bis zur Integration via offiziellen TypeScript- oder PHP-SDKs.

Wer dieses Portal liest

aYOUne ist eine multi-tenant Business-as-a-Service-Plattform mit ~330 Microservices, die hinter einem einheitlichen Routing-Pattern https://{module}-api.ayoune.app zusammenfließen. Wer Drittsysteme anbinden möchte (Shop, ERP, Custom-Frontend, Mobile-App, Zapier-ähnliche Flows) findet hier sämtliche Bausteine. Im Gegensatz zum Admin-Handbook, das für Customer-Admins gedacht ist, richtet sich dieses Portal an Entwickler.

Schnellnavigation

Thema Inhalt
Erste Schritte Account, JWT-Token, erster API-Call
REST-API Basics Auth-Header, JSON-Envelope, Pagination
Webhooks Outbound-Webhooks abonnieren
SDKs TypeScript- und PHP-SDK
CORS & Auth Browser-Calls, Token-Lifecycle
Error Codes HTTP-Statuscodes & payload.error

Architekturüberblick

Jedes Domänen-Modul (crm, cms, marketing, automation, config, ...) exponiert eine eigene Express-API. Alle Routen folgen demselben Schema:

GET    https://crm-api.ayoune.app/consumers
GET    https://crm-api.ayoune.app/consumers/:id
POST   https://crm-api.ayoune.app/consumers
PATCH  https://crm-api.ayoune.app/consumers/:id
DELETE https://crm-api.ayoune.app/consumers/:id

Hinter den Kulissen verwendet jede Route den createAPIHandler-Faktor und antwortet mit dem standardisierten defaultAPIAnswer-Envelope:

{
  "payload": { "data": [...], "entries": 42 },
  "meta": { "pageInfo": { "totalEntries": 42 } }
}

Welche Module gibt es?

Eine vollständige Modul-Liste mit Routing-Hosts und Highlight-Endpoints findest du in der API-Reference. Über 25 Domänen — von crm über cms, marketing, automation, ai, chat, config bis zu hub — stehen dir mit demselben Auth-Token offen, sofern dein Tenant das jeweilige Paket gebucht hat.

Nächster Schritt

Erste Schritte — Token holen, ersten Call machen.

Work with this page

Ready-made instructions for your AI tool. Copy, paste, go — the AI fetches the content itself via the address in the text.

Summarise the steps for me The essentials, in the right order.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/developer-portal/developer-portal-bersicht.md
The complete collection: https://ayoune.com/en/docs/developer-portal.md

Summarise the content for me.

- First, in two sentences: what is this about?
- Then the steps in the order I need to take them.
- One line per step, in plain language.
- At the end: what I should have ready beforehand.

Leave out nothing I need in order to actually finish.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.
Help me set this up Step by step, asking me as you go.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/developer-portal/developer-portal-bersicht.md
The complete collection: https://ayoune.com/en/docs/developer-portal.md

Walk me through the setup step by step.

- First tell me what I need to have ready (access, data, time).
- Then take me through ONE step at a time. Wait for my "next".
- For each step, say how I can tell that it worked.
- If something goes wrong, ask me for the exact message instead of guessing.

If the instructions leave a point open, tell me so rather than inventing it.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.
Help me with a problem Narrow down the cause instead of guessing.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/developer-portal/developer-portal-bersicht.md
The complete collection: https://ayoune.com/en/docs/developer-portal.md

Help me narrow down a problem.

- First ask me what I observe and what I expected instead.
- From that, derive the most likely causes consistent with this source.
- For each cause, give me ONE test that confirms or rules it out.
- Order them so the cheapest test comes first.

Do not guess. If the source does not cover the problem, tell me where I should
look next.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.
Explain it in plain words No jargon, from the ground up.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/developer-portal/developer-portal-bersicht.md
The complete collection: https://ayoune.com/en/docs/developer-portal.md

Explain the content so that someone without prior knowledge understands it.

- Start with the purpose: why does this exist at all?
- Explain technical terms in half a sentence on first use.
- One everyday comparison where it genuinely holds — none where it limps.
- At the end: the three things worth remembering.

Do not shorten by dropping conditions. A simplification that hides a
prerequisite is a false statement.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.
A checklist to tick off To follow along while you do it.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/developer-portal/developer-portal-bersicht.md
The complete collection: https://ayoune.com/en/docs/developer-portal.md

Turn this into a **tick-off checklist** for practical use.

- Exactly one action per item, in the imperative.
- Order it so that no item depends on a later prerequisite.
- Prerequisites and pitfalls as indented sub-items.
- End with an acceptance step: how do I know everything is right?
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.
Build it into my project Concrete code for my use case.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/developer-portal/developer-portal-bersicht.md
The complete collection: https://ayoune.com/en/docs/developer-portal.md

Help me build this into my project.

- First ask me about language, environment and what I am trying to achieve.
- Then give a minimal, runnable example — no ellipses standing in for code.
- Name the error cases I must handle and how they surface.
- State the limits: timeouts, quotas, permissions.

Use only what the source actually describes. Do not invent fields, parameters
or endpoints — an invented call costs me more time than it saves.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.

Was this article helpful?

👎 No (0)
Leave a comment