DOCSEARCHbyAlgolia
Submit Docs

The Movie Database (TMDB) API

website·Indexed 30 days ago

https://first-nominees.vercel.app

Open API documentation for TMDB, providing endpoints to retrieve data on movies, TV shows, and people. Features include searching for TV shows, fetching top-rated and popular content, managing user ratings, retrieving release dates, and accessing translations and credits for entertainment media.

Tokens
12.3K
Snippets
173
Records
184
Agent score
74%

What's inside TMDB

  2. Retrieve movie collection details by ID

    Use the GET /3/collection/:collection_id endpoint to retrieve detailed information about a specific movie collection. The :collection_id path parameter must be provided to identify the target collection.
    curl -X GET "https://<api-domain>/3/collection/{collection_id}"

  3. Retrieve information about a specific keyword

    Use the GET /3/keyword/:keyword_id endpoint to retrieve detailed information about a specific keyword. Replace :keyword_id in the URL path with the unique identifier of the keyword you wish to query.
    GET /3/keyword/{keyword_id}

  4. Retrieve movie or TV credit details using /3/credit/:credit_id

    Use the GET /3/credit/:credit_id endpoint to fetch detailed information about a specific movie or TV credit. The request requires a credit_id as a path parameter.
    curl "https://api.example.com/3/credit/{credit_id}"

  5. Retrieve details for a specific TV episode

    Use the GET endpoint /3/tv/:series_id/season/:season_number/episode/:episode_number to retrieve detailed information about a specific TV episode. You must provide the series ID, the season number, and the episode number as path parameters.
    GET /3/tv/:series_id/season/:season_number/episode/:episode_number

  6. Retrieve TV episode group details

    Use the GET /3/tv/episode_group/:tv_episode_group_id endpoint to retrieve detailed information about a specific TV episode group. The :tv_episode_group_id path parameter is required to identify the group.
    curl -X GET "https://<api-base-url>/3/tv/episode_group/{tv_episode_group_id}"

  7. Understand the Client Dashboard Process

    When a client logs into the portal, the dashboard provides a high-level overview of their activity and financial status. The dashboard displays the following key statistics:

    • Open instructions
    • Posted instructions
    • Total instructions
    • Cash balance retrieved from the ERP system

    Additionally, the dashboard includes a table listing recently created instructions for quick access and tracking.

  8. Understand the Investment Portal system architecture

    The Investment portal architecture consists of three primary layers: the Client Browser, the Portal Server, and the Dynamics Business Central server (which acts as the back office and primary data source).

    Communication Flows:

    • Client to Portal: Users access the portal via HTTPS using a browser (Mobile, Tablet, or PC) and authenticate using Email and Password.
    • Portal to Business Central: Bi-directional communication occurs over HTTPS and SFTP.
      • HTTPS: Used for API and Web Service calls. The Portal calls Web Services published on Business Central, while Business Central calls APIs published on the Portal.
      • SFTP: Used specifically for downloading reports and transferring supporting documents for instructions.
    • Security: All communications are secured. HTTPS requests are authenticated using keys, tokens, and credentials before being processed by the servers.

  9. Execute the settlement instruction workflow

    The settlement process follows a specific sequence from client submission to ERP integration:

    1. Authentication: The client logs into the portal using their existing email and password.
    2. Instruction Selection: The client navigates to the settlement module and selects the desired instruction type.
    3. Submission: The client provides the required instruction details and submits the request.
    4. Approval (Conditional): If an approval setup is configured, an approver workflow is initiated and relevant approvers are notified. If no approval setup exists, the instruction bypasses this step and is pushed directly to the ERP.
    5. ERP Integration: Once approved (or if no approval is required), the instruction is pushed to the ERP system.
    6. Finalization: A user processes and updates the instruction within the ERP, then syncs the updated instruction back to the portal.

  10. Implement Workshop UI and Validation Requirements

    The following functional requirements from the Workshop must be implemented:

    1. Add tooltips to the 'import' and 'attach document' buttons on the instruction creation page.
    2. Implement validation for imported files to ensure all required information is provided by the client.
    3. Update the dashboard to display the client's total investment at a glance.
    4. Improve the overall user-friendliness of the portal.

  11. Approve a pending instruction request

    To approve a pending instruction, follow these steps:

    1. Navigate to the approval request page and select a pending request.
    2. In the pending request table, locate the action column for the specific request and click 'Approve'.
    3. Enter the required approval token and click 'Submit'.

    Depending on the system configuration:

    • If only one approver is required and the current user is that approver, the instruction is approved immediately.
    • If multiple approvers are required, subsequent approvers must repeat this same flow before the instruction is fully approved.

  12. Implement Client Onboarding and Account Management Requirements (RFP)

    The following requirements from the Request Functional Procedure (RFP) define the client-facing capabilities for account opening and management:

    • Account Opening (CS001): Capture all necessary data including Client name, bank account details (for coupons), currency, email, telephone, BVN, NIN, date of birth/registration, TIN, and address. (Status: GAP - Requires Customization)
    • Agreement Execution (CS002): Facilitate the signing, storage, and downloading of executed agreements. (Status: GAP - Requires Customization)
    • Document Upload (CS003): Allow clients to upload onboarding documents in specified formats. (Status: GAP - Requires Customization)
    • Email Verification (CS004): Provide a mechanism for users to confirm their email address for indemnity/verification. (Status: FIT)
    • Account Access (CS005): Grant account access upon completion of the account opening form. (Status: FIT)
    • Verification Status (CS006): Allow users to view account status, including automated data verification results and activation status. (Status: FIT)
    • Password Reset (CS007): Provide a secure method for users to reset forgotten passwords. (Status: FIT)
    • Username Reset (CS008): Provide a secure method to reset usernames via verified email or phone. (Status: GAP - Requires Customization)
    • Data Updates (CS009): Allow clients to update account details, address, and email, protected by security layers such as 2-Factor Authentication (2FA). (Status: FIT)