Step 2b — Save user-confirmed column mappings
Source Creator
Step 2b — Save user-confirmed column mappings
PUT /source-creator/sessions//mappings
PUT
Step 2b — Save user-confirmed column mappings
This endpoint requires authentication. Include your Bearer token in the Authorization header.
Description
PUT /source-creator/sessions//mappings Description: Saves the user-confirmed column mappings, source name/label, optional aggregator name, and optional royalty type. Validates that at least ROYALTY or COUNT is mapped, warns if ISRC (or ASSET_TITLE+ASSET_ARTIST) isn’t mapped, warns if period-type columns lack adateFormat, and — when the session has a dataClass set —
checks confirmed mappings against the canonical fact-schema’s
required columns. sourceName must match ^[a-zA-Z0-9_-]+$.
Also fires a best-effort smart source-name suggestion after saving.
Authorization:
- Required role:
adminor higher
Code Examples
Authorizations
JWT Authorization header using the Bearer scheme. Format: "Bearer {token}"
Path Parameters
Session ID
Body
application/json
Alphanumeric, underscores, and hyphens only. Normalized as the RoyaltySource name on save.
Pattern:
^[a-zA-Z0-9_-]+$Example:
"my_new_dsp"
Display label; defaults to sourceName if omitted.
Optional per-source rights type. Case-insensitive on input; the
matched canonical value (as listed) is persisted. Omit, send null,
or send an empty string for "unknown" — anything else that doesn't
case-insensitively match one of these values is a 400.
Available options:
Master, Publishing, Mechanical, Performance, Sync