> ## Documentation Index
> Fetch the complete documentation index at: https://apidocs.royalti.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Bulk delete Splits
> **Bulk Delete Revenue Split Configurations**
This endpoint requires authentication. Include your Bearer token in the Authorization header.
## Description
**Bulk Delete Revenue Split Configurations**
The Bulk Delete Revenue Split Configurations endpoint (`/split/bulk/delete`) allows users to delete multiple revenue split configurations in bulk.
**Method:**\
`POST`
**Request Payload:**
The request payload should be a JSON object with an array of revenue split configuration IDs (ids) to be deleted.
| Parameter | Type | Required | Description |
| --------- | --------- | -------- | ----------------------------------------------------------------- |
| ids | string\[] | Yes | An array of revenue split configuration IDs (UUIDs) to be deleted |
> This request deletes multiple revenue split configurations with the specified UUIDs. Ensure you provide the necessary authentication token in the request header and the IDs of the configurations you want to delete in the request payload.
## Code Examples
```javascript Node.js theme={null}
const response = await fetch('https://api.royalti.io/split/bulk/delete', {
method: 'POST',
headers: {
'Authorization': `Bearer ${token}`,
'Content-Type': 'application/json'
},
body: JSON.stringify({
"ids": [
{}
]
})
});
const data = await response.json();
console.log(data);
```
```python Python theme={null}
import requests
response = requests.post(
'https://api.royalti.io/split/bulk/delete',
headers={
'Authorization': f'Bearer {token}'
},
json={"ids":[{}]}
)
data = response.json()
print(data)
```
```bash cURL theme={null}
curl -X POST https://api.royalti.io/split/bulk/delete \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"ids":[{}]}'
```
## OpenAPI
````yaml post /split/bulk/delete
openapi: 3.0.0
info:
title: Royalti.io API
description: "# Royalti API\r\n\r\nThis is the Royalti music royalty management platform API server.\r\n\r\n## Overview\r\n\r\nThe Royalti API provides comprehensive music royalty management services including:\r\n- Music publishing and writer management\r\n- Royalty processing and analytics\r\n- DDEX integration for music industry standards\r\n- File processing and pattern recognition\r\n- Payment processing and distribution\r\n\r\n## Authentication\r\n\r\nThe API uses JWT-based authentication with multiple protection levels:\r\n- Public endpoints for basic operations\r\n- Protected endpoints requiring valid JWT tokens\r\n- Admin endpoints for administrative functions\r\n\r\n## Features\r\n\r\n- Multi-dimensional royalty analytics\r\n- CWR (Collective Works Registration) support\r\n- DDEX integration for music metadata\r\n- Advanced file processing with pattern recognition\r\n- Real-time data processing with queue system"
version: 2.6.0
contact:
name: Royalti.io Support
email: support@royalti.io
url: https://royalti.io
license:
name: Proprietary
url: https://royalti.io/terms
servers:
- url: https://api.royalti.io
description: Production server
- url: https://api-dev.royalti.io
description: Development server
- url: http://localhost:8084
description: Local development
security:
- bearerAuth: []
tags:
- name: Accounting
description: Accounting and financial transaction operations
- name: DDEX
description: DDEX operations (ERN/MEAD, messages, delivery, providers)
- name: Label
description: Label management operations
- name: Internal Webhooks
description: Internal system webhooks for royalty processing and downloads
- name: Payment Webhooks
description: Payment processor webhook endpoints
- name: Billing Webhooks
description: Stripe billing and subscription webhooks
- name: Infrastructure Webhooks
description: Cloudflare domain and SSL webhooks
- name: Distribution Webhooks
description: Digital distribution platform webhooks (FUGA)
paths:
/split/bulk/delete:
post:
tags:
- Splits
summary: Bulk delete Splits
description: >-
**Bulk Delete Revenue Split Configurations**
The Bulk Delete Revenue Split Configurations endpoint
(`/split/bulk/delete`) allows users to delete multiple revenue split
configurations in bulk.
**Method:**
`POST`
**Request Payload:**
The request payload should be a JSON object with an array of revenue
split configuration IDs (ids) to be deleted.
| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| ids | string[] | Yes | An array of revenue split configuration IDs
(UUIDs) to be deleted |
> This request deletes multiple revenue split configurations with the
specified UUIDs. Ensure you provide the necessary authentication token
in the request header and the IDs of the configurations you want to
delete in the request payload.
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
ids:
type: array
items:
type: string
format: uuid
description: >-
An array of revenue split configuration IDs (UUIDs) to be
deleted
required:
- ids
example:
ids:
- a8787d14-1149-4b10-9e29-7ef054de8c3f
- b9898e25-2250-5c21-af3a-8fg165ef9d4g
- c0a0af36-3361-6d32-bg4b-9gh276fg0e5h
responses:
'200':
description: Split configurations deleted successfully
content:
application/json:
schema:
type: object
properties:
message:
type: string
deletedCount:
type: integer
errors:
type: array
items:
type: string
example:
message: Split configurations deleted successfully
deletedCount: 3
errors: []
'400':
description: Bad Request - Invalid IDs
content:
application/json:
schema:
type: object
properties:
message:
type: string
errors:
type: array
items:
type: string
example:
message: Some split configurations could not be deleted
errors:
- >-
Split configuration with ID
a8787d14-1149-4b10-9e29-7ef054de8c3f not found
'401':
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'404':
description: Not Found
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'500':
description: Internal Server Error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- bearerAuth: []
components:
schemas:
Error:
type: object
properties:
success:
type: boolean
example: false
error:
type: object
properties:
code:
type: string
message:
type: string
details:
type: array
items:
type: string
securitySchemes:
bearerAuth:
type: http
scheme: bearer
bearerFormat: JWT
description: >-
JWT Authorization header using the Bearer scheme. Format: "Bearer
{token}"
````