API Endpoints
| Environment | URL |
|---|---|
| Production | https://crm.broadstripes.com/api/automated_imports |
| Staging | https://groton.broadstripes.com/api/automated_imports |
HTTP Specifications
Request Method
POST - All automated import requests must use the POST methodAuthentication
Include your authentication token in the HTTP header:Content Types
For CSV Data
- Content-Type:
multipart/form-data - Content-Disposition:
form-data; name="automated_import[source_document]"; filename="your-file.csv"
For JSON Data
- Content-Type:
application/json - Content-Disposition: Not required (or use
application/json)
Request Examples
CSV Import with curl
JSON Import with curl
Response Format
Success Response
Status Code:200
Response Structure:
Error Responses
The API will return appropriate HTTP status codes and error messages for:- Invalid authentication tokens
- Malformed data
- Configuration issues
- Server errors
Code Examples
Ruby CSV Import
Ruby JSON Import
Data Format Requirements
CSV Format
- Headers Required: First row must contain field names
- Field Names: Must match Broadstripes field names exactly
- Encoding: UTF-8 recommended
- File Size: No explicit limit, but consider timeout settings
JSON Format
- Structure: Array of objects, where each object represents one record
- Field Names: Must match Broadstripes field names exactly
- Data Types: Use appropriate JSON data types (strings, numbers, booleans)
Field Name Examples
Common field names that map to Broadstripes:first_name,last_nameemployer,departmentaddress1,address2,city,state,zipphone,email- Custom field names (must match exactly as configured in your project)
ZIP File Support (CSV Only)
For CSV imports, you can send a ZIP file containing multiple CSV files with specific names:people_modifications.csvaddress_modifications.csvphone_modifications.csvemployment_modifications.csv
Best Practices
Performance
- Batch Size: Consider breaking large datasets into smaller batches
- Timeout: Set appropriate timeout values (example shows 600 seconds)
- Retry Logic: Implement retry mechanisms for failed requests
Security
- HTTPS Only: Always use HTTPS endpoints
- Token Security: Keep authentication tokens secure and rotate them regularly
- Data Validation: Validate data before sending to reduce errors
Error Handling
- Check Response Codes: Always verify the HTTP response status
- Parse Error Messages: Handle and log API error responses appropriately
- Monitor Import Status: Use the web interface to monitor import progress and results
Rate Limits
While not explicitly documented, consider implementing reasonable delays between requests to avoid overwhelming the API. Monitor your import success rates and adjust timing as needed.Testing
Always test your integration against the staging environment before using production:- Use the staging URL for initial development
- Test with small datasets first
- Verify data appears correctly in the Broadstripes interface
- Confirm your authentication tokens work properly