Reports APIsPrerequisites
- A Divine API Account: Ensure registration at reports.divineapi.com to access your dashboard for API keys.
- Test API Key: This key, found within your dashboard, allows the generation of a limited number of test PDF reports to ensure smooth integration.
- Live report generation necessitates purchasing reports post-successful testing.
Step 1: Importing the Postman Collection
Facilitate your integration with our comprehensive Postman collection:
- Access Your Dashboard: Sign into your Divine API account and navigate to the dashboard.
- Find the Postman Collection Link: Seek the direct link for the Postman collection tailored for our API.
- Import into Postman: Utilize the link to import the collection into Postman, equipped with preset request formats and endpoints.
Step 2: Configuring the Request
Prepare your API call as follows:
- Request URL: https://pdf.divineapi.com/numerology/v1/report
- Method: POST
Step 3: Setting Up Authorization
Ensure your API requests are secure:
- Go to Postman's Authorization tab.
- Select Bearer Token as the authorization type.
- Input your Bearer Token in the provided field for request authentication.
Note: You will find the Bearer token in your Dashboard along with the Live & Test keys
Step 4: Configuring the Request Body
In the body of your request, select raw and choose JSON as the format. Then, input the following parameters:
{
"api_key": "your API Key",
"full_name": "Rahul Kumar",
"day": "01",
"month": "12",
"year": "1998",
"gender": "male",
"company_name": "Divine API",
"company_url": "https://divineapi.com/",
"company_email": "admin@divineapi.com",
"company_mobile": "+91 9557787052",
"company_bio": "Discover the best Horoscope API and Tarot API services at Divineapi.com...",
"logo_url": "https://divineapi.com/assets/logo.png",
"footer_text": "Divine API",
"report_code": "QUEEN-OF-HEARTS"
}
{4.1 Explanation of Body Parameters
- api_key: Your unique API key for accessing the service. This key authenticates your requests to ensure security and proper access control.
- full_name: The full name of the individual for whom the report is being generated. This is used to personalize the report.
- day: The birth day of the individual, used to calculate specific astrological details. Format as a two-digit number (e.g., "01").
- month: The birth month of the individual. This should be formatted as a two-digit number (e.g., "12") and is crucial for accurate astrological analysis.
- year: The birth year of the individual, essential for creating the natal chart and performing accurate astrological calculations.
- hour: The hour of birth, based on a 24-hour clock, used to determine the ascendant and other time-sensitive aspects of the natal chart.
- min: The minute of birth, which helps refine the accuracy of the astrological predictions and calculations.
- sec: The second of birth, providing even further precision for the astrological analysis, though not always required.
- gender: The gender of the individual ("male" or "female"). Some astrological analyses might differentiate interpretations based on gender.
- place: The birthplace (city, state, country) of the individual. This information is used to calculate the local sidereal time and hence the ascendant.
- lat: The latitude of the birthplace, essential for calculating the precise position of celestial bodies at the time of birth.
- lon: The longitude of the birthplace, used alongside latitude to accurately calculate the astrological chart.
- tzone: The time zone of the birthplace, represented as a decimal (e.g., "5.5" for IST). This is critical for adjusting the birth time to GMT for accurate chart calculations.
- lan: Language code for the report (e.g., "en" for English). This determines the language in which the report is generated.
- company_name: Your company's name. This allows for branding of the report with your business name.
- company_url: Your company's website URL. This can be included in the report for brand visibility and credibility.
- company_email: The contact email for your company. This might be used for customer inquiries or support related to the report.
- company_mobile: Your company's contact mobile number, providing another avenue for customer contact or support.
- company_bio: A short bio or description of your company. This is a branding opportunity to share more about your services.
- logo_url: The URL of your company logo. This image will be included in the report for branding purposes.
- footer_text: Custom text to appear in the footer of each page of the report. This can be used for copyright notices, contact information, or promotional messages.
API Keys
Your dashboard provides two API keys:
- Production API Key: For all live requests.
- Test API Key: Enables up to 15-20 test PDF reports for integration trials without quota impact.
Available Report Codes
Branding Options
The request body includes branding options allowing you to customize the PDF reports with your company's identity:
- company_name: Your company's name.
- company_url: Your company's website URL.
- company_email: Your contact email.
- company_mobile: Your contact mobile number.
- company_bio: A short bio or description of your company.
- logo_url: The URL of your company logo.
- footer_text: Custom text to appear in the footer of each page.
Step 5: Sending the Request
After configuring your request, click the "Send" button. You should receive a response similar to the following:
{
"success": 1,
"data": {
"name": "Rahul Kumar",
"report_url": "https://reports.divinestore.net/r/1133717091112331546726-52"
}5.1 Response Body Explained
- success: Indicates the request was successful (1 = success).
- data: Contains the report details.
- name: The name of the individual the report pertains to.
- report_url: The URL where the generated report can be accessed.
Conclusion
This guide facilitates the integration and testing of the Numerology PDF API via Postman, enabling the provision of detailed, branded numerology reports. For further assistance, our customer service team is readily available to support you.