{"info":{"_postman_id":"d76f92ef-619e-4b9d-94fa-b6f3e152161c","name":"Radmin API","description":"

Radmin API

A hands-on Postman collection for testing radmin's JSON API across development, staging, and production. Open the shared collection in Postman, select the right environment, add your own radmin credentials, create a token, then run the examples.

\n
Production writes are real writes. Check DS-METRO-ID before creating events, importing queue items, approving queue work, or flushing queues.
\n

🚀 Fast Start

Open the shared Radmin API collection in Postman.
Select the environment you want to test against: Radmin API Development, Radmin API Staging, or Radmin API Production.
Fill these environment variables in your selected Postman environment:
- api_email: the same email address you use for radmin.
- api_password: the same password you use for radmin.
- metro_id: the active metro/property id for the request context.
\n
Run Authentication / Create Token.
The token response stores jwt and user_id in your selected environment.
Run the API examples. Requests that operate in a metro send DS-METRO-ID: {{metro_id}}.

🌎 Environments

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Environment	`radmin_url`	Use for
Development	`https://radmin.dothebay.baw`	Local development and Docker/Caddy testing.
Staging	`https://stadmin.dostuffmedia.com`	Pre-production smoke testing before deploy.
Production	`https://radmin.dostuffmedia.com`	Real radmin data. Use deliberately.

Each user should store their own api_email and api_password in their Postman environment. The production environment is safe to use for testing reads, but write requests create or update real radmin data.

🗂️ Collections

Collections let radmin build reusable groups of events, venues, artists, tastemakers, and curated picks for apps and pages. Use them when you need to create or update the sets of content that a frontend experience will display.

Use the Collections folder for the concrete requests. A collection group owns an ordered list of collections. Collections can be automatic (all_events, venue, promo_user, tastemaker, band, query) or curated. Curated collection items are managed through collection_items_attributes on collection create/update payloads; there is no standalone collection-item endpoint in this API collection.

🔐 Auth

POST /api/tokens uses radmin email/password validation and returns the existing radmin JWT shape.
The collection sends Authorization: Bearer {{jwt}} automatically after token creation.
Metro context belongs in DS-METRO-ID, not request bodies.
Missing or invalid bearer tokens return JSON 401.

📄 Pagination

Most CRUD list endpoints accept page and per_page. Collection group endpoints currently return arrays because they follow the existing radmin-v2 collection API shape.
Default page size is 50; maximum is 100.
Normal CRUD list responses include current_page, per_page, total_pages, and total_count.
Pending and duplicate queue responses skip expensive total counts and return current_page, per_page, and next_page.

🎟️ Events And Queues

Radmin has two event creation paths: direct event CRUD for approved events, and event imports for review queues. Pick the path that matches the workflow you are automating.

✅ Create Approved Events

Use POST /api/events when the event is ready to go live. This is normal CRUD creation and creates an approved event directly in radmin.

🔎 Preview Duplicate Handling

Use POST /api/event_dupe_checks as a dry run before importing scraped or external data. It accepts event-shaped data, creates nothing, and returns the duplicate gate result radmin would use: ignored event, obvious duplicate, obvious repeating duplicate, obvious ongoing duplicate, pending replacement, or potential duplicate.

🧾 Import Events For Review

Use POST /api/event_imports when you want radmin to create unapproved review work. With no queue value, or with queue: \"auto\", radmin behaves like the scraper importer: obvious duplicates are skipped, normal candidates enter pending review, and potential duplicates enter duplicate review.

📥 Force Pending Review

Set queue: \"pending\" on POST /api/event_imports to force a normal pending queue item. This does not create EventDupe records because normal pending review does not need comparison targets.

🧬 Force Duplicate Review

Set queue: \"duplicate\" on POST /api/event_imports to create a duplicate queue item. If you pass potential_dupe_id or potential_dupe_ids, radmin uses those approved events as comparison targets. If you omit them, radmin generates potential dupes from the posted event using its scraper duplicate logic. If no approved comparison event can be found, the request is rejected instead of creating broken duplicate state.

📚 Review Queue Items

Use GET /api/event_queues/pending to list unapproved non-duplicate pending events. Use GET /api/event_queues/duplicates to list unapproved duplicate-review events and their comparison matches. Queue list responses are paginated and intentionally avoid total counts because these queues can be slow. Follow pagination.next_page until it is empty.

🔒 Approve Or Flush Queues

Queue approval and flush endpoints use the same Redis locks as radmin. If a flush is already running, list and flush requests return HTTP 423 with error: queue_locked. Treat that as \"try again later,\" not as a failed import.

🧪 Common Workflows

Grant Event Editor access: list roles with GET /api/roles, find or create the user with the Users requests, then create a user permission with POST /api/users/:user_id/permissions. Event Editor is role id 8.
Add an artist: use POST /api/artists. You can include cover_image_url to pull the image by URL.
Add an approved event with images: use POST /api/events with venue_id, category_id, optional band_ids, and image URLs such as cover_image_url, poster_image_url, or share_image_url.

🛡️ Rate Limits

/api/tokens is throttled by IP.
API resource routes are throttled by SHA256 fingerprint of the raw Authorization header.
Default limits are 5,000 requests per 5 minutes and 300 write requests per 5 minutes per auth header. That write limit is roughly one write per second per token.
Throttled responses return HTTP 429 with { \"error\": \"rate_limited\" } plus Retry-After, X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers.

\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[{"content":"Radmin API","slug":"radmin-api"}],"owner":"2966202","collectionId":"d76f92ef-619e-4b9d-94fa-b6f3e152161c","publishedId":"2sBXwtr9qX","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"FF6C37"},"publishDate":"2026-06-17T18:41:49.000Z"},"item":[{"name":"Agent Instructions","item":[],"id":"e598acf7-8ddf-4538-8968-cbc3a77afd06","description":"

Radmin API Agent Instructions

Use these instructions when an agent is working with the Radmin JSON API from any HTTP client, script, integration, or shared API collection.

Goal

Use the Radmin API to inspect, create, or update radmin data through documented JSON endpoints. Prefer API requests over browser automation when the API covers the workflow.

Connection Setup

Choose the correct environment before making requests:
- Development: https://radmin.dothebay.baw
- Staging: https://stadmin.dostuffmedia.com
- Production: https://radmin.dostuffmedia.com
\n
Authenticate with the same email address and password used to log in to radmin.
Send metro context with the DS-METRO-ID header. Do not put metro_id in request bodies unless an endpoint specifically documents it.
Use Content-Type: application/json for JSON requests.

Authentication

POST /api/tokens with email and password.
Read the returned JWT token.
Send API requests with Authorization: Bearer <token>.
If a request returns 401, request a fresh token before retrying.

Production Safety

Production writes are real. Before running create, update, approve, import, or flush requests:

Confirm the base URL is intentional.
Confirm DS-METRO-ID is the correct active metro/property.
Prefer read requests first when discovering IDs.
Do not approve or flush queues unless the operator explicitly asks for it.

Common Workflows

Grant Event Editor access:

List roles with GET /api/roles.
Find or create the user with the Users API.
List the user's existing permissions.
Create a permission with POST /api/users/:user_id/permissions.
Event Editor is role id 8.

Create an artist with an image:

Use POST /api/artists.
Include cover_image_url when the image should be pulled by URL.
Store the returned artist id for event band_ids.

Create an approved event with images:

Find or create the venue.
Find or create artists and pass their ids in band_ids.
Use POST /api/events with venue_id, category_id, dates, and times.
Include cover_image_url, poster_image_url, or share_image_url when image URLs are available.

Import events for review:

Use POST /api/event_dupe_checks first when you want to preview how radmin will classify duplicate or pending work.
Use POST /api/event_imports for unapproved queue work.
Use queue: \"auto\" unless the operator explicitly wants pending or duplicate review forced.

Response Handling

Store returned resource ids for later requests.
Treat 401 as an auth/token problem.
Treat 423 with queue_locked as \"try again later.\"
Treat 429 with rate_limited as a real throttle. Read Retry-After before retrying, and use X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset when reporting or scheduling retries.

Reporting Back

When reporting results, include:

Environment/base URL used.
Metro id sent in DS-METRO-ID.
Endpoint paths called.
Created or updated resource ids.
Any API warnings or errors, especially duplicate, queue-lock, or rate-limit responses.

\n","_postman_id":"e598acf7-8ddf-4538-8968-cbc3a77afd06","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt}}"}]},"isInherited":true,"source":{"_postman_id":"d76f92ef-619e-4b9d-94fa-b6f3e152161c","id":"d76f92ef-619e-4b9d-94fa-b6f3e152161c","name":"Radmin API","type":"collection"}}},{"name":"Authentication","item":[{"name":"Create Token","event":[{"listen":"test","script":{"type":"text/javascript","exec":["if (pm.response.code === 201) {"," var json = pm.response.json();"," pm.environment.set('jwt', json.token);"," pm.environment.set('user_id', json.user.id);"," if (json.user.preferences && json.user.preferences.length) {"," pm.environment.set('user_preference_id', json.user.preferences[0].id);"," }","}"],"id":"8423f737-b510-417a-8f62-e78f4b5b6948"}}],"id":"f4e5bbb3-a87d-4b53-9585-2aaafe0920a2","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"noauth","isInherited":false},"method":"POST","header":[{"key":"Content-Type","value":"application/json"}],"body":{"mode":"raw","raw":"{\n \"email\": \"{{api_email}}\",\n \"password\": \"{{api_password}}\"\n}"},"url":"{{radmin_url}}/api/tokens","description":"

Endpoint: POST /api/tokens

Authenticates a radmin user by email address with the usual Devise password validation and returns a JWT for API requests. Metro context for API requests comes from the DS-METRO-ID header, not this token body.

\n","urlObject":{"path":["api","tokens"],"host":["{{radmin_url}}"],"query":[],"variable":[]}},"response":[],"_postman_id":"f4e5bbb3-a87d-4b53-9585-2aaafe0920a2"}],"id":"f004f480-5ad4-4a20-9909-d9243aa3f254","_postman_id":"f004f480-5ad4-4a20-9909-d9243aa3f254","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt}}"}]},"isInherited":true,"source":{"_postman_id":"d76f92ef-619e-4b9d-94fa-b6f3e152161c","id":"d76f92ef-619e-4b9d-94fa-b6f3e152161c","name":"Radmin API","type":"collection"}}},{"name":"Metros","item":[{"name":"List Metros","id":"3342d42a-f2a2-4e43-97c6-3d68f102ebd0","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"key":"DS-METRO-ID","value":"{{metro_id}}"}],"url":"{{radmin_url}}/api/metros","description":"

Returns active metros available through radmin API auth.

Returns one active metro when the authenticated user has access.

Returns roles the authenticated user can assign for the active metro. Event Editor is role id 8.

Looks up one user by exact email for the requested metro context. Returns user: null when no user exists.

User responses include preferences, an array of the user's network preference records. Each preference includes id, subdomain_id, subdomain, metro_id, profile name, email preference flags, enabled/vip flags, activity timestamps, and created/updated timestamps. Use the preference id when updating an existing preference through preferences_attributes on PUT /api/users/:id.

Returns one user with permissions scoped to the requested metro.

Endpoint: GET /api/users/:id/events

Returns approved active-metro events that the user has voted on. This is intentionally separate from /api/events?user_id=... so voted events do not conflict with event creator ownership.

Creates a user when absent. If the email already exists, returns the existing user with created: false and ensures the active metro preference exists. The response includes preferences; Postman stores the first preference id as user_preference_id when present.

Updates supported user fields for the requested metro context.

To update an existing user preference, send Rails-style nested attributes under user.preferences_attributes. The API accepts either an array of preference attribute hashes or the classic indexed hash shape (\"0\", \"1\", etc.). Include the preference id from GET /api/users/:id or GET /api/users?email=...; without an id, Rails treats the nested attributes as a new preference. Supported nested preference fields are subdomain_id, profile_name, mail_list, send_band_emails, and auto_event_redirect. profile_name is the user's vanity/profile slug for that property. The API attaches the active metro from DS-METRO-ID while validating preference profile-name uniqueness.

Users

User API responses include the user's active network preferences in user.preferences. Preferences are the per-property/subdomain settings that drive things like profile vanity, mail-list membership, event redirect behavior, and email notification flags.

The create-user endpoint returns an existing user when the email is already present and also ensures the active metro preference exists. Use GET /api/users/:id or GET /api/users?email=... to capture a preference id, then send nested preferences_attributes to PUT /api/users/:id when updating preference fields.

For nested preference updates, Rails accepts either an array of preference hashes or the classic indexed hash shape. Include the nested preference id when changing an existing preference. If the id is omitted, Rails treats the nested attributes as a new preference record. The API attaches the active metro from DS-METRO-ID, so clients should not send metro_id directly.

\n","_postman_id":"46bb6f48-387f-4cf9-a6ca-12e16b9908d3","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt}}"}]},"isInherited":true,"source":{"_postman_id":"d76f92ef-619e-4b9d-94fa-b6f3e152161c","id":"d76f92ef-619e-4b9d-94fa-b6f3e152161c","name":"Radmin API","type":"collection"}}},{"name":"Permissions","item":[{"name":"List User Permissions","id":"bd4d877c-bb1f-4afc-8304-874bbd0fed6e","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"key":"DS-METRO-ID","value":"{{metro_id}}"}],"url":"{{radmin_url}}/api/users/{{user_id}}/permissions","description":"

Lists permissions for a user on the requested metro.

Creates a metro-scoped permission for a user. Use role id 8 to grant Event Editor.

Deletes one permission by id. Delete the permission with role id 8 to remove Event Editor.

Endpoint: GET /api/venues

Endpoint: GET /api/venues/:id

Endpoint: GET /api/venues/:id/events

Returns approved active-metro events for the selected venue. Equivalent to GET /api/events?venue_id={{venue_id}}.

Endpoint: POST /api/venues

Creates a venue in the active metro. To attach a cover image, pass cover_image_url in JSON or use multipart venue[cover_image][picture]. venue[image_logs_attributes] is optional metadata.

Endpoint: POST /api/venues

Creates a venue and pulls the cover image by URL through CarrierWave. Equivalent nested form field: venue[cover_image][remote_picture_url].

Endpoint: PUT /api/venues/:id

Replaces the venue cover image by URL. Multipart venue[cover_image][picture] is also supported; venue[image_logs_attributes] is optional metadata.

Endpoint: GET /api/artists

Endpoint: GET /api/artists/:id

Endpoint: POST /api/artists

Creates an artist. To attach a cover image, pass cover_image_url in JSON or use multipart artist[cover_image][picture] / band[cover_image][picture]. image_logs_attributes is optional metadata.

Endpoint: POST /api/artists

Creates an artist and pulls the cover image by URL through CarrierWave. Equivalent nested form field: artist[cover_image][remote_picture_url] or band[cover_image][remote_picture_url].

Endpoint: PUT /api/artists/:id

Replaces the artist cover image by URL. Multipart artist[cover_image][picture] or band[cover_image][picture] is also supported; image_logs_attributes is optional metadata.

Endpoint: GET /api/pages

Endpoint: GET /api/pages/:id

Endpoint: POST /api/pages

Creates a page in the active metro. Supports title, uri, content, custom_css, and custom_js.

Endpoint: PUT /api/pages/:id

Updates page content and optional custom code fields. Supported custom code fields are custom_css and custom_js.

Endpoint: DELETE /api/pages/:id

Endpoint: GET /api/categories

Lists categories for the active metro. Optional filters: kind=event|events|venue|venues, conference_id, query, and title.

Endpoint: GET /api/categories?kind=events

Lists event categories for the active metro.

Endpoint: GET /api/categories?kind=venues

Lists venue categories for the active metro.

Endpoint: GET /api/categories/:id

Endpoint: POST /api/categories

Creates an event category in the active metro. Use for_venue: false for event categories.

Endpoint: POST /api/categories

Creates a venue category in the active metro. Use for_venue: true for venue categories.

Endpoint: PUT /api/categories/:id

Endpoint: DELETE /api/categories/:id

Endpoint: GET /api/url_redirects

Lists URL redirects for the active metro. Requires a superuser token.

Endpoint: GET /api/url_redirects/:id

Returns one active-metro URL redirect.

Endpoint: POST /api/url_redirects

Creates an unpublished URL redirect for the active metro. origin and destination must be URL-shaped values. origin is unique within the active metro. The API ignores live; publish through POST /api/url_redirects/:id/publish or POST /api/url_redirects/publish.

Endpoint: PUT /api/url_redirects/:id

Updates an active-metro URL redirect. If the redirect is already live, changing origin or destination refreshes the Redis cache through the existing model callback.

Endpoint: POST /api/url_redirects/:id/publish

Publishes one redirect by writing its Redis key and marking the record live when the write succeeds.

Endpoint: POST /api/url_redirects/publish

Publishes all unpublished URL redirects for the active metro.

Endpoint: DELETE /api/url_redirects/:id

Deletes one active-metro URL redirect. Existing model callbacks remove the Redis key.

URL Redirects

URL redirects are superuser-only and scoped to the active metro from DS-METRO-ID. Create or update the database record first, then publish it so radmin writes the Redis redirect entry and marks the record live. The API does not accept live on create/update; use the publish endpoints instead.

The normal lifecycle is:

Create a redirect with POST /api/url_redirects. This stores origin, destination, and status_code in the database with live: false.
Review or update it while unpublished with GET /api/url_redirects/:id and PUT /api/url_redirects/:id.
Publish one redirect with POST /api/url_redirects/:id/publish, or publish all unpublished redirects for the active metro with POST /api/url_redirects/publish.
After publish succeeds, radmin stores the Redis key url-redirect:<metro-domain>:<origin> pointing at destination and marks the record live: true.

When a live redirect's origin or destination changes, the existing model callback removes the old Redis key and writes the new one. Deleting a redirect removes its Redis key. origin must be unique within a metro. The same origin can exist in another metro, but a duplicate origin for the same DS-METRO-ID returns 422.

\n","_postman_id":"c7ae3230-0e4c-46af-bcbb-887bb31b62f9","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt}}"}]},"isInherited":true,"source":{"_postman_id":"d76f92ef-619e-4b9d-94fa-b6f3e152161c","id":"d76f92ef-619e-4b9d-94fa-b6f3e152161c","name":"Radmin API","type":"collection"}}},{"name":"Collections","item":[{"name":"List Collection Groups","event":[{"listen":"test","script":{"type":"text/javascript","exec":["if (pm.response.code === 200) {"," var groups = pm.response.json() || [];"," if (groups.length) {"," pm.environment.set('collection_group_id', groups[0].id);"," }","}"],"id":"c2bb1178-9ceb-42cc-bb1c-cacc745d4c57"}}],"id":"a21d6493-4064-4d22-892b-d736d5a41f8c","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"key":"DS-METRO-ID","value":"{{metro_id}}"}],"url":"{{radmin_url}}/api/collection_groups","description":"

Endpoint: GET /api/collection_groups

Returns collection groups and their nested collections for the active metro context.

Endpoint: GET /api/collection_groups/:id

Returns one collection group with nested collections.

Endpoint: POST /api/collection_groups

Creates a collection group in the active metro. metro_id is set from DS-METRO-ID.

Endpoint: PUT /api/collection_groups/:id

Endpoint: POST /api/collection_groups/:id/positions

Reorders collections inside a group. Send collection_ids in the desired order.

Endpoint: GET /api/collection_groups/:collection_group_id/collections

Lists collections nested under a collection group.

Endpoint: GET /api/collection_groups/:collection_group_id/collections/:id

Endpoint: POST /api/collection_groups/:collection_group_id/collections

Creates an automatic all-events collection. position and metro_id are set by radmin.

Endpoint: POST /api/collection_groups/:collection_group_id/collections

Creates a curated collection. Curated items are passed as collection_items_attributes with target_type, target_id, position, and optional _destroy.

Endpoint: PUT /api/collection_groups/:collection_group_id/collections/:id

Updates a nested collection. For curated collections, send collection_items_attributes to add, reorder, revive, or remove curated items.

Endpoint: DELETE /api/collection_groups/:collection_group_id/collections/:id

Endpoint: DELETE /api/collection_groups/:id

Deletes a collection group and its nested collections.

🗂️ Collections

Collections are the radmin-managed configuration that powers radmin-v2 collection groups and DoXYZ runtime collection responses.

How The Pieces Fit

A collection_group is the top-level container. It has a key, display metadata, and an ordered list of nested collections.
A collection describes one lane of content inside the group. It controls title, slug, key, layout, active state, content type, identity IDs, and query config.
Radmin writes the configuration. DoXYZ reads active groups by key, preloads active collections in position order, builds an Elasticsearch _msearch request, and merges the returned hits back into a group/collections/items response.
The ES runtime currently targets indexes such as events_search_v1, venues_v1, bands_v1, and users_v1, depending on the collection type or curated target type.

Collection Types

all_events: event-backed collection using query config filters and sorting.
venue: event-backed collection filtered to venue.id.
band: event-backed collection filtered through nested bands.id.
promo_user: event-backed collection filtered by promo_user_ids.
tastemaker: event-backed collection filtered by tastemaker_ids.
query: raw ES query JSON stored in query_json.
curated: explicit ordered items. Send collection_items_attributes with target_type, target_id, position, and optional _destroy.

Practical Notes

DS-METRO-ID supplies metro context; do not put metro_id in request bodies.
Radmin sets collection group and collection metro_id from the active property.
Radmin sets a new collection position to the end of its group.
Use POST /api/collection_groups/:id/positions to reorder collections inside a group.
There is no standalone collection-item controller in this Postman collection. Manage curated items through collection create/update payloads.

\n","_postman_id":"90cc6c5d-edfc-4037-8f5b-55a82faac3a1","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt}}"}]},"isInherited":true,"source":{"_postman_id":"d76f92ef-619e-4b9d-94fa-b6f3e152161c","id":"d76f92ef-619e-4b9d-94fa-b6f3e152161c","name":"Radmin API","type":"collection"}}},{"name":"Events","item":[{"name":"List Events","id":"e6cdd06c-98fd-41e8-9887-e2fa23c90cff","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"key":"DS-METRO-ID","value":"{{metro_id}}"}],"url":"{{radmin_url}}/api/events","description":"

Endpoint: GET /api/events

Lists approved events for the active metro. Optional filters: venue_id, scraper_id, and artist_id.

Endpoint: GET /api/events?venue_id=:venue_id

Lists approved active-metro events for a venue. Equivalent nested route: GET /api/venues/:id/events.

Endpoint: GET /api/events?scraper_id=:scraper_id

Lists approved active-metro events created from scrapes associated with the scraper.

Endpoint: GET /api/events?artist_id=:artist_id

Lists approved active-metro events whose lineup includes the artist/band id.

Endpoint: GET /api/events/:id

Endpoint: POST /api/events/:event_id/votes

Creates a vote on the active-metro event for a specific user id. Body accepts either top-level user_id or nested vote.user_id. Response includes created: true with HTTP 201 for a new vote, or created: false with HTTP 200 when the user already voted on the event.

Endpoint: POST /api/events

Creates an approved event in the active metro. Required event fields mirror the radmin form: title, venue_id, category_id, begin_date, begin_time, and event_setting_attributes.event_type. Use band_ids to create the event lineup. Vanity URLs are managed through the has-one event setting: JSON clients can send event.event_setting_attributes.vanity; form or multipart clients can send event[event_setting_attributes][vanity].

Endpoint: POST /api/events

Creates an event and pulls images by URL through CarrierWave. Use cover_image_url, poster_image_url, and share_image_url; the API maps those to nested remote_picture_url image params.

\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt}}"}]},"isInherited":true,"source":{"_postman_id":"d76f92ef-619e-4b9d-94fa-b6f3e152161c","id":"d76f92ef-619e-4b9d-94fa-b6f3e152161c","name":"Radmin API","type":"collection"}},"urlObject":{"path":["api","events"],"host":["{{radmin_url}}"],"query":[],"variable":[]}},"response":[],"_postman_id":"c97f7ec6-60ee-443a-96bf-ba4ceb441301"},{"name":"Create Event With Multipart Images","event":[{"listen":"test","script":{"type":"text/javascript","exec":["if ([200, 201].includes(pm.response.code)) {"," pm.environment.set('event_id', pm.response.json().event.id);","}"],"id":"98c61ecd-acac-4ee6-a860-18034a080866"}}],"id":"0071fb5d-ec64-4baf-99d1-83e693de6633","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"DS-METRO-ID","value":"{{metro_id}}"}],"body":{"mode":"formdata","formdata":[{"key":"event[title]","value":"Radmin API Image Event","type":"text"},{"key":"event[permalink]","value":"radmin-api-image-event","type":"text"},{"key":"event[begin_date]","value":"2026-06-01","type":"text"},{"key":"event[begin_time(4i)]","value":"20","type":"text"},{"key":"event[begin_time(5i)]","value":"00","type":"text"},{"key":"event[venue_id]","value":"{{venue_id}}","type":"text"},{"key":"event[category_id]","value":"{{event_category_id}}","type":"text"},{"key":"event[event_setting_attributes][event_type]","value":"single_day","type":"text"},{"key":"event[event_setting_attributes][show_in_main_listings]","value":"1","type":"text"},{"key":"event[event_setting_attributes][vanity]","value":"radmin-api-image-event","type":"text"},{"key":"event[cover_image][picture]","type":"file","value":""},{"key":"event[poster_image][picture]","type":"file","value":""},{"key":"event[share_image][picture]","type":"file","value":""},{"key":"event[image_logs_attributes][0][info]","value":"Source and usage permission for the cover image.","type":"text"},{"key":"event[image_logs_attributes][0][image_type]","value":"cover_image","type":"text"},{"key":"event[image_logs_attributes][0][user_id]","value":"{{user_id}}","type":"text"},{"key":"event[image_logs_attributes][0][app]","value":"Radmin","type":"text"},{"key":"event[image_logs_attributes][1][info]","value":"Source and usage permission for the poster image.","type":"text"},{"key":"event[image_logs_attributes][1][image_type]","value":"poster_image","type":"text"},{"key":"event[image_logs_attributes][1][user_id]","value":"{{user_id}}","type":"text"},{"key":"event[image_logs_attributes][1][app]","value":"Radmin","type":"text"},{"key":"event[image_logs_attributes][2][info]","value":"Source and usage permission for the share image.","type":"text"},{"key":"event[image_logs_attributes][2][image_type]","value":"share_image","type":"text"},{"key":"event[image_logs_attributes][2][user_id]","value":"{{user_id}}","type":"text"},{"key":"event[image_logs_attributes][2][app]","value":"Radmin","type":"text"},{"key":"gigs[band_id][]","value":"{{artist_id}}","type":"text"}]},"url":"{{radmin_url}}/api/events","description":"

Endpoint: POST /api/events

Multipart example for uploading event images with the same field names used by the radmin event form. Use event[cover_image][picture], event[poster_image][picture], or event[share_image][picture]. The matching event[image_logs_attributes] source fields are optional metadata; omit them when you do not need image logs. URL-based uploads can also use nested event[cover_image][remote_picture_url], event[poster_image][remote_picture_url], or event[share_image][remote_picture_url]. Vanity URLs use event[event_setting_attributes][vanity].

Endpoint: PUT /api/events/:id

Partial updates are supported. Include band_ids only when replacing the event lineup; omitting it leaves existing gigs unchanged. To update an event vanity URL, send nested event_setting_attributes.vanity in JSON or event[event_setting_attributes][vanity] in form/multipart requests. The API updates the existing has-one event setting when the nested id is omitted.

Endpoint: PUT /api/events/:id

Replaces event images by URL through CarrierWave. Any omitted image field is left unchanged.

Endpoint: PUT /api/events/:id

Replaces event images with multipart uploads. Use the same event[cover_image][picture], event[poster_image][picture], and event[share_image][picture] fields as create. The matching event[image_logs_attributes] source fields are optional metadata; omit them when you do not need image logs.

Endpoint: POST /api/event_dupe_checks

Runs radmin's duplicate checks without creating an event. The response reports ignored, obvious duplicate, obvious repeating duplicate, obvious ongoing duplicate, pending replacement, and potential duplicate outcomes. Use potential_dupes from this response as explicit potential_dupe_ids when importing directly to the duplicate queue.

Endpoint: POST /api/event_imports

Creates an unapproved event for pending or duplicate review. With no queue value, or with queue: \"auto\", the API uses the scraper-style duplicate detector: the event lands in the normal pending queue when no approved potential duplicate is found and lands in the duplicate queue when the detector finds an approved event with the same metro, begin date, and venue. Use queue: \"pending\" to place the event directly in pending review. Use queue: \"duplicate\" to place it in duplicate review; pass potential_dupe_id / potential_dupe_ids when the caller already knows the approved matches, or omit them and radmin will generate matches from the posted event. Metro context comes from DS-METRO-ID.

Endpoint: POST /api/event_imports

Direct duplicate placement. If potential_dupe_id or potential_dupe_ids are present, they must point at approved events in the active metro. If omitted, radmin computes potential dupes from the posted event using the same potential-dupe logic as scraper imports. The API creates the EventDupe records used by the duplicate review UI.

Endpoint: GET /api/event_queues/pending

Lists unapproved non-duplicate pending events for the active metro. If a pending flush is already running, returns HTTP 423 with error: queue_locked.

Endpoint: GET /api/event_queues/duplicates

Lists unapproved pending events that duplicate detection marked as possible duplicates. Responses include the pending event plus likely approved matches. If a duplicate flush is already running, returns HTTP 423 with error: queue_locked.

Endpoint: POST /api/event_queues/approve

Approves one pending event. Send event_id for a single event or event_ids for a batch.

Endpoint: POST /api/event_queues/update_from_pending

Applies a pending duplicate event onto an approved event using the same model method as the browser duplicate queue.

Endpoint: POST /api/event_queues/flush_pending

Queues the existing background flush for all pending non-duplicate events in the active metro. If a pending flush is already running, returns HTTP 423 with error: queue_locked.

Endpoint: POST /api/event_queues/flush_pending_subset

Queues the existing background flush for selected pending non-duplicate events. If a pending flush is already running, returns HTTP 423 with error: queue_locked.

Endpoint: POST /api/event_queues/flush_duplicates

Queues the existing background flush for all pending duplicate events in the active metro. If a duplicate flush is already running, returns HTTP 423 with error: queue_locked.

Endpoint: POST /api/event_queues/flush_duplicates_subset

Queues the existing background flush for selected pending duplicate events. If a duplicate flush is already running, returns HTTP 423 with error: queue_locked.

Endpoint: DELETE /api/events/:id