Executive Summary

PyjamaHR offers APIs and custom white-labeling options that enable agencies, SaaS founders, and consultancies to build branded recruitment solutions or micro-SaaS products on top of the PyjamaHR platform. This guide explains how to leverage PyjamaHR APIs for custom job listings, career pages, and agency offerings—covering real-world use cases, integration steps, pricing models, and best practices based on actual customer scenarios.

Detailed Overview

What Is White-Labeling and Micro‑SaaS on PyjamaHR?

White-labeling with PyjamaHR means rebranding the platform or its components (like the career page or job listings) with your own logo, domain, and branding—removing PyjamaHR’s name and visuals. Micro‑SaaS refers to building a niche SaaS product or service (e.g., a recruitment portal for a specific industry or region) on top of PyjamaHR’s APIs, often embedding job listings or application workflows into your own site or product.

Why Use PyjamaHR for White‑Label or Micro‑SaaS?

Brand Ownership: Offer recruitment solutions under your own brand, ideal for agencies and consultancies.
Custom Experience: Fully control the look, feel, and workflow on your website or client portals.
API-Driven Flexibility: Fetch jobs, candidates, and more to power custom UIs or workflows.
Scalable Infrastructure: Leverage PyjamaHR’s backend, AI, and automation without building from scratch.
Monetization: Build and sell your own SaaS or agency-branded solutions.

Typical Use Cases

Agencies offering branded recruitment portals to clients.
SaaS founders embedding job boards or application forms into their own platforms.
Companies wanting a fully branded career page on a custom domain.
Micro-SaaS products targeting specific geographies or industries.

Step-by-Step Guide: Building Your White‑Label or Micro‑SaaS Solution

Prerequisites

PyjamaHR Account: Ensure you have an active account (AppSumo tiers, premium, or custom plan).
API Access: Confirm API access is enabled for your plan (contact support if unsure).
Custom Plan: For full white-labeling (removing branding, custom domain), a custom plan or one-time fee may be required.
Technical Skills: Ability to work with REST APIs and basic web development.

1. Define Your White‑Label or Micro‑SaaS Requirements

Branding Needs: Logo, colors, domain, removal of “Powered by PyjamaHR.”
Functionality: Job listing, candidate application, resume parsing, etc.
Integration Points: Website, Webflow, custom portal, etc.
User Roles: Will you offer this to clients, internal teams, or as a SaaS?

2. Request API Access and Documentation

Contact Support: Ask for API documentation and access token.
- Example: “Please find the API docs for fetching the list of jobs. [API Docs Link]”
- Example: “Token: [Your API Token]”
Confirm Plan Eligibility: API access is available on certain plans or as a custom add-on.

3. Fetch and Display Job Listings via API

API Endpoint: Use the /jobs endpoint to fetch job listings.
Frontend Integration: Build your own UI to display jobs (React, Vue, Webflow, etc.).
- Custom Styling: Since the default embed (iframe) is not fully customizable, using the API lets you apply your own CSS and layout.
- Example: “I want to view the lists only, and apply some basic CSS to it so it will fit with my page.”

Sample Steps:
1. Obtain your API token from support.
2. Make a GET request to the jobs endpoint.
3. Parse the response and render jobs in your desired format.
4. Style the UI to match your brand.

Screenshot Callout: Show where to enter the API token and a sample API response.

4. Handle CORS and Security

CORS Issues: If making API calls from the frontend, you may encounter CORS errors.
- Solution: Request PyjamaHR to whitelist your domain or use a backend proxy.
- “I tried the API, but I'm getting CORS Error since I'm only able to make the call on the front-end.”
- Support can resolve CORS issues on request.

5. Remove PyjamaHR Branding (White‑Labeling)

Default Embed: The iframe embed includes “Powered by PyjamaHR” and cannot be removed except via a custom plan.
- “It's not possible to remove the PyjamaHR footer from the iframe currently, this is only possible with a custom plan.”
Custom Plan: Pay a one-time fee (e.g., $400) or monthly add-on for full white-labeling (branding removal, custom domain).
- “We can enable the 'Hide PyjamaHR' branding option for you as a custom build for a fee of $400 payable one-time.”
API Approach: Building your own UI via API gives you full control over branding.

6. Custom Domain and Advanced White‑Labeling

Custom Domain: Only available via custom plan; not supported on standard plans.
- “Custom domain is not possible for career page” (standard plans).
Full Platform White‑Label: For agencies or SaaS providers, discuss requirements with support for a tailored plan (minimum user count, server costs, etc.).
- “Minimum company size requirements we usually have to whitelabel is 25 users minimum, so that's 25*$15/month.”

7. Advanced: Build Micro‑SaaS or Agency Solutions

Multi‑Client Support: Offer branded portals to multiple clients (requires custom plan and possibly higher-tier pricing).
API-Driven Automation: Use PyjamaHR APIs to automate job posting, candidate management, and reporting.
Exporting Data: Use the Compare view to download candidate data in Excel.

Advanced Usage & Best Practices

Power User Tips

Custom UI: Use the API to build a fully custom job board or application workflow.
Domain Whitelisting: Always request domain whitelisting early to avoid CORS issues.
Brand Consistency: Use your own CSS and assets for a seamless brand experience.
API Security: Never expose your API token in public frontend code; use a backend proxy if needed.

Optimization Strategies

Cache API Responses: To reduce API calls and improve performance.
Error Handling: Gracefully handle API errors and fallback scenarios.
Mobile Responsiveness: Ensure your custom UI works well on all devices.

Do’s and Don’ts

Do:
- Confirm your plan supports API and white-label features before starting.
- Use the API for maximum flexibility and branding control.
- Communicate your exact requirements to support for accurate pricing and timelines.

Don’t:
- Expect to remove PyjamaHR branding from the default embed without a custom plan.
- Expose sensitive API tokens in client-side code.
- Assume all features (custom domain, full white-label) are included in standard plans.

Troubleshooting & Common Issues

Common Issues

1. CORS Errors
- Symptom: “CORS Error since I'm only able to make the call on the front-end.”
- Solution: Request PyjamaHR to whitelist your domain or use a backend proxy.

2. Unable to Remove Branding
- Symptom: “Powered by PyjamaHR” visible on embedded forms/pages.
- Solution: Only removable via custom plan (one-time fee or monthly add-on).

3. API Access Not Available
- Symptom: “I was told that there is API, but not sure if my plans have it.”
- Solution: Contact support to confirm eligibility and enable API access.

4. Custom Domain Not Supported
- Symptom: “Custom domain is not possible for career page.”
- Solution: Only available on custom plans; discuss with support.

5. Delays in Support
- Symptom: “Delay from support makes me really worried…”
- Solution: Follow up via email and request a call for urgent needs.

Comprehensive FAQ

1. Can I remove “Powered by PyjamaHR” from the career page or embed?
Only with a custom plan (one-time fee or monthly add-on). Not possible on standard plans.

2. Can I use my own domain for the career page?
Only via a custom plan. Standard plans do not support custom domains.

3. How do I get API access?
Contact support to enable API access and receive documentation and your token.

4. What if I get a CORS error using the API?
Request PyjamaHR to whitelist your domain, or use a backend server to proxy requests.

5. Can I style the embedded job list to match my website?
Not with the default iframe embed. Use the API to build your own UI for full control.

6. What is the cost for white-labeling?
Typically a one-time fee (e.g., $400) or a monthly add-on. Minimum user counts and server costs may apply for full platform white-label.

7. Can I offer PyjamaHR as a branded solution to my clients (agency/micro‑SaaS)?
Yes, but you’ll need a custom plan. Discuss your requirements with support for pricing and setup.

8. How long does white-label setup take?
Usually 2 weeks from agreement and payment.

9. Can I export candidate data?
Yes, via the Compare view in the platform.

10. Is there an agency or reseller tier?
Custom plans are available for agencies and resellers; contact support for details.

11. Can I add custom CSS to the embed?
Not directly. Use the API to build your own job list for full CSS control.

12. What if I need to support multiple clients or regions?
Discuss multi-client or multi-region needs with support for a tailored solution.

API Documentation: [Request from support or see your onboarding email]
Custom Plan Inquiry: Contact support for white-label, custom domain, or agency pricing.
Career Page Embed: For simple use cases, use the iframe embed (branding not removable).
Candidate Data Export: Use Compare view in PyjamaHR.
Related Articles:
- [How to Embed Your PyjamaHR Career Page]
- [Managing API Tokens and Security]
- [Customizing Your Job Board with PyjamaHR APIs]

Real-World Scenarios

Agency in UAE: Offers PyjamaHR under their own brand to local consultancies, using API and custom domain (custom plan required).
Startup: Wants to embed job listings on their site with custom CSS—uses API for full control.
Retail Micro‑SaaS: Founder wants to offer recruitment as a service to retail business owners—API and white-labeling via custom plan.

Still have questions?
Contact PyjamaHR support for a tailored consultation and to unlock API or white-label features for your business.

This guide is based on real customer conversations and current PyjamaHR capabilities as of June 2024. For the latest updates or to discuss your unique requirements, please reach out to our support team.

How to Build a White‑Label or Micro‑SaaS Solution Using PyjamaHR APIs: The Complete Guide