Skip to main content

Authentication

๐Ÿ” API Key Required

To use the Juleb ERP API, you must have a valid API key. Currently, API keys are provided exclusively through our customer success or sales team.

Getting Your API Keyโ€‹

๐Ÿข Existing Customers

Contact your dedicated customer success manager or reach out to our support team.

support@juleb.com

๐Ÿ†• New to Juleb?

Speak with our sales team to learn about Juleb ERP and get started with API access.

sales@juleb.com

Authentication Method: OAuth 2.0โ€‹

The Juleb ERP API uses OAuth 2.0 for secure authentication. This industry-standard protocol ensures your data remains protected while providing seamless access to your ERP system.

How It Worksโ€‹

๐Ÿ”„ Authentication Flow
  1. Request API Key - Contact our team
  2. Receive API Key - Secure token provided
  3. Make API Calls - Include in headers

Adding Authentication to Your Requestsโ€‹

Include your API key in the Authorization header of every request:

Authorization: Bearer {YOUR_API_KEY}
๐Ÿ’ก Replace the Placeholder

Always replace {YOUR_API_KEY} with your actual API key. Never commit API keys to version control!

API Base URL and Versioningโ€‹

URL Structureโ€‹

https://{ACCOUNT_NAME}.juleb.com/api/v1/{endpoint}
๐Ÿท๏ธ URL Components Explained
  • {ACCOUNT_NAME}: Your unique Juleb account identifier (subdomain)
  • api: API namespace
  • v1: API version (ensures backward compatibility)
  • {endpoint}: Specific API endpoint (e.g., inventory/product)

Examples by Accountโ€‹

https://demo.juleb.com/api/v1/inventory/product
https://demo.juleb.com/api/v1/pos/order
https://demo.juleb.com/api/v1/resources/partner

Security Best Practicesโ€‹

Security Best Practicesโ€‹

โœ… Do
  • Store API keys in environment variables
  • Use server-side applications for API calls
  • Rotate API keys regularly
  • Monitor API usage and logs
  • Use HTTPS for all requests
โŒ Don't
  • Hardcode API keys in your source code
  • Expose API keys in client-side JavaScript
  • Share API keys via email or chat
  • Use API keys in URLs or query parameters
  • Commit API keys to version control

Testing Your Authenticationโ€‹

Try the Interactive API Explorerโ€‹

Before building your integration, test your API key with our interactive documentation:

๐Ÿงช API Explorer

Interactive documentation where you can test endpoints directly in your browser

๐Ÿ‘‰ Open API Explorer (opens in new tab)

Quick Authentication Testโ€‹

Test your API key
curl -X GET \
-H "Authorization: Bearer YOUR_API_KEY" \
"https://YOUR_ACCOUNT.juleb.com/api/v1/inventory/product?limit=1"

Expected Response:

{
"data": [...],
"meta": { "count": 1, "total": 150 },
"pagination": { ... }
}

Common Authentication Errorsโ€‹

Status CodeErrorSolution
401UnauthorizedCheck your API key and ensure it's included in the Authorization header
403ForbiddenYour API key may not have permission for this endpoint or account
404Not FoundVerify your account name in the URL is correct
429Rate LimitedSlow down your requests or contact support for higher limits
๐ŸŽฏ Next Steps

Now that you're authenticated, learn how to explore API queries to get the most out of your API calls!