Getting results back

How MusiMap intelligence returns to your platform through API, files, and push delivery.

MusiMap has processed your music. How does the intelligence get back into your platform? Pulling stored results through API calls is only one option. MusiMap supports several delivery models, and they can be combined in the same integration.

For where MusiMap fits overall, see How MusiMap integrates. For how content reaches MusiMap, see Getting data into MusiMap.

Immediate response

For request/response workflows such as on-demand MusiTag or applicable on-demand product calls, the result comes back as part of the request workflow:

Your platform → MusiMap → Result

Your application receives the intelligence in the same interaction and stores or routes it as needed. See Tagging for on-demand MusiTag.

Retrieve results

For stored catalogue intelligence, your application can query MusiMap through the API when it needs results. This covers catalogue intelligence, analysis results, search and profile use cases, and status endpoints where appropriate for asynchronous jobs.

Status polling helps track long-running ingestion jobs, but it is one part of a broader delivery story rather than the complete result-delivery model on its own.

Push results

MusiMap can deliver completed results back to your environment. Results can be delivered through:

  • Webhook notification and delivery when batches or jobs complete;
  • Customer-managed Amazon S3 for result files;
  • SFTP for result files;
  • MusiMap-managed storage for customer retrieval;
  • CSV and JSON result files where appropriate for catalogue workflows.
Keep your existing downstream workflow

MusiMap can return completed batch intelligence through the storage or delivery channel your platform already consumes. Large catalogue workflows do not need to retrieve results one track at a time. API access and file or push delivery can coexist in the same integration.

Getting results back from MusiMap MusiMap results flow to your platform through API response, API retrieval, webhooks, S3, and SFTP or result files. MusiMap results API response API retrieval Webhook Customer S3 SFTP / files Your platform and workflows
API, webhook, storage, and file delivery are all valid paths. Models can be combined in the same integration.

Combining delivery models

Delivery models are often combined. For example:

  • immediate API results for exceptional individual tracks;
  • batch CSV delivery for normal catalogue ingestion;
  • webhook notification when a batch is ready;
  • API access for applications that query stored intelligence dynamically.

MusiMap intelligence can flow back into your existing catalogue or application. You do not need to use MusiMap as your operational catalogue UI.

Continue reading

How MusiMap integrates

Product models and catalogue integration choices.

Getting data into MusiMap

Storage, inputs, and ingestion timing.