Bulk Update Segments
Updates multiple segments in one request. The array of segments can contain up to 1000 records.
If any of the records contain an error the whole request would fail and none of the requested segments get updated. The error response contains a message for only the one segment that failed validation, with the corresponding index in the array.
You may specify component and/or price point by using either the numeric ID or the handle:gold syntax.
Authorization
BasicAuth The username is a Maxio Chargify API key. The password is x.
In: header
Path Parameters
ID or Handle for the Component
ID or Handle for the Price Point belonging to the Component
Request Body
application/json
items <= 1000Response Body
application/json
application/json
curl -X PUT "https://example.com/components/string/price_points/string/segments/bulk.json" \ -H "Content-Type: application/json" \ -d '{}'{ "segments": [ { "id": 0, "component_id": 0, "price_point_id": 0, "event_based_billing_metric_id": 0, "pricing_scheme": "stairstep", "segment_property_1_value": "string", "segment_property_2_value": "string", "segment_property_3_value": "string", "segment_property_4_value": "string", "created_at": "2019-08-24T14:15:22Z", "updated_at": "2019-08-24T14:15:22Z", "prices": [ { "id": 0, "component_id": 0, "starting_quantity": 0, "ending_quantity": 0, "unit_price": "string", "price_point_id": 0, "formatted_unit_price": "string", "segment_id": 0 } ] } ]}Bulk Create Segments POST
Creates multiple segments in one request. The array of segments can contain up to `2000` records. If any of the records contain an error the whole request would fail and none of the requested segments get created. The error response contains a message for only the one segment that failed validation, with the corresponding index in the array. You may specify component and/or price point by using either the numeric ID or the `handle:gold` syntax.
Issue advance invoice POST
Issues an invoice in advance for a subscription's next renewal date. For the most part, advance invoices function like any other invoice, except they are issued early and have special behavior upon being voided. For more information on advance invoices, including eligibility for generating one, see [Issue Invoice In Advance](https://maxio.zendesk.com/hc/en-us/articles/24252026404749-Issue-Invoice-In-Advance). A subscription can only have one advance invoice per billing period. Attempting to issue an advance invoice when one already exists returns an error. Regeneration of the invoice can be forced with the params `force: true`, which voids an advance invoice if one exists and generates a new one. If no advance invoice exists, a new one is generated. Consider using either the create or preview endpoints for proforma invoices to preview this advance invoice before using this endpoint to generate it.