The publish action will start the publish process for everything in the import queue. This can take a while, so if you send in an oncomplete parameter set to a url, we’ll send a request to that when it’s done. If you send an email as your argument for oncomplete, we’ll email that instead. With this publish job id, you can use the list command to get all the final track ids in case you want to download them or update your external system. Please keep in mind that while your tracks are technically live at the time of publishing, there will still be a slight delay before they’re available from search while they’re being indexed. You can also create a job separate from your site’s main publishing job by creating a job and using the job_id returned from that call in subsequent calls to /api/import/upload and /api/import/publish.
An email or url that will be called when this upload’s job is published. One per job, overwrites if already exists
Publish a specific job_id. Default is your site’s main publishing job, but you can also publish to a specific job_id i.e. as created by /api/import/createJob