Overview
The Organization Setup endpoint is called once when a customer enables the supplies module in your platform. This endpoint creates the organization profile, shipping addresses, and user accounts in Sticker’s system.When to Call This Endpoint
1
User Enables Feature
A customer clicks “Enable Supplies” or similar in your platform
2
Validate Permissions
Verify the user has admin rights to enable organization-wide features
3
Collect Required Data
Gather organization details, addresses, and user list
4
Call Setup Endpoint
Send data to Sticker to provision the organization
5
Store Integration ID
Save the returned profile ID for future API calls
API Endpoint
https://api.sticker.com (production) or https://sandbox.api.sticker.com (sandbox)
Authentication
Include your Partner API Key in the Authorization header:Request Format
OAuth Flow (Recommended)
If you have an OAuth integration with Sticker:Manual Data Push
If you don’t use OAuth, send the complete organization structure:Request Parameters
Organization Object
The legal or display name of the organization
Primary contact email for the organization (must be valid email format)
Primary phone number (E.164 format recommended: +1-555-123-4567)
Array of shipping/billing addresses (at least one required)
Address Object
Street address, P.O. box, company name
Apartment, suite, unit, building, floor, etc.
City, district, suburb, town, or village
State, province, or region (2-letter abbreviation for US/CA)
ZIP or postal code
Two-letter country code (ISO 3166-1 alpha-2)
Whether this is the default shipping address
Users Array
List of users to create in the organization (at least one admin required)
User’s email address (unique identifier)
User’s first name
User’s last name
User role:
admin or member (defaults to member)Partner Org ID
Your internal identifier for this organization. Used to link future handshake requests.
Response Format
Success Response (201 Created)
Whether the operation succeeded
Action taken:
created or updated (if organization already existed)Sticker’s unique identifier for this organization profile
Your internal org ID (echoed back for verification)
Number of user accounts created
Number of addresses added to the profile
Error Responses
400 Bad Request
400 Bad Request
- Missing required fields
- Invalid email format
- Invalid country/state codes
- No primary address specified
401 Unauthorized
401 Unauthorized
409 Conflict
409 Conflict
update: true to modify existing organization500 Internal Server Error
500 Internal Server Error
Code Examples
Updating Organizations
To update an existing organization, send the same request with updated data. Sticker will:- Match based on
partner_org_id - Update changed fields
- Add new addresses/users
- Preserve existing data not included in the request
Updates are additive. Existing users and addresses are not deleted unless explicitly specified.
Best Practices
Data Validation
Data Validation
- Validate email addresses before sending
- Ensure phone numbers are in E.164 format
- Verify state/country codes match ISO standards
- Confirm at least one primary address exists
Error Handling
Error Handling
- Implement retry logic with exponential backoff
- Log all API responses for debugging
- Display user-friendly error messages
- Handle partial failures gracefully
Data Storage
Data Storage
- Store the returned
profile.idin your database - Link it to your internal organization ID
- Keep track of integration status
- Log setup timestamp for audit trails
User Experience
User Experience
- Show progress indicators during setup
- Confirm successful enablement
- Provide clear next steps
- Offer support contact if setup fails

