Get Import Mappings (Events)
GET /importMappings?target=events
/importMappings?target=eventsRequired Tokens
| Field | Type | Required | Description |
|---|---|---|---|
| Bearer | Authorization: Bearer <api-key> | Optional | Your API key. Pass it as the Bearer token on every request. |
| Organization token | x-Organization-Token | Optional | Run **Get Tokens** in the **Organization API** collection, then set `orgToken` as a variable here. This target is org-scoped, so an event token will not authorize it. |
The same endpoint as Get Import Mappings, called for the org-scoped events target. It exists as a
separate request because the token audience differs by target and that is the easiest thing to get
wrong: proposalLineItems takes an event token, events takes an organization token, and neither
substitutes for the other.
The organization token is minted against the Organization API's own OAuth audience, so Get Tokens in
this collection cannot fetch it. Run Get Tokens in the Organization API collection and set orgToken
as a variable here.
Requires OrganizationAdmin.
An events mapping is tied to an event type
Event attributes are defined per event type, so a mapping built against one type references keys that only
exist on that type. The type it was built against is recorded inside configuration, not as a
first-class field, and this endpoint does not filter on it — the client reads it back to label the mapping
and to warn when it is applied against a different type.
A mapping saved against no event type is legal and stays loadable: an untyped import carries the target's first-class fields only.
Response
Same shape as Get Import Mappings, with target reading Events.
Errors
| Status | Meaning |
|---|---|
400 | target is missing or is not a registered import target. |
403 | The caller lacks OrganizationAdmin, or sent an event token instead of an organization token. |