EtMDB REST API v1

Name: EtMDB REST API v1 API
Brand: EtMDB REST API v1
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaVideo Processingoauth227 EndpointsREST

For Agents

Search Ethiopian Movie Database records — movies, cast, crew, companies, cinema schedules, and showtimes — by title, name, or keyword to power Ethiopian film discovery.

Install Jentic One Beta

Connect the EtMDB REST API v1 to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the EtMDB REST API v1, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with EtMDB REST API v1 API.

Search Ethiopian movies by title and retrieve cast, crew, and metadata

Look up cinema details, schedules, and showtimes for a given movie or location

Find filmography and credits for an Ethiopian actor, director, or production company

GET STARTED

Start building with EtMDB REST API v1 API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use EtMDB REST API v1 API for, with concrete tasks.

★ Movie discovery feed for an Ethiopian film app

A consumer app pulls movies, genre listings, and people from EtMDB to power its discovery and search screens. Title queries hit /api/v1/movie/search/{movie_title} for fast lookups, while category browsing uses /api/v1/genre/searchall/{movie_genre_type} to fetch full lists. Cast detail screens stitch /api/v1/movie-cast/search and /api/v1/people/search together for each title.

GET /api/v1/movie/search/{movie_title} for the user's query, then for each result GET /api/v1/movie-cast/search/{movie_title} and /api/v1/genre/search/{movie_title} to populate the detail screen.

Cinema showtime lookup and ticketing assistant

A ticketing chat assistant resolves a user's 'what's playing tonight at Cinema X?' request by calling /api/v1/cinema-shedule-showtime/searchall/{param} or /api/v1/cinema-detail/search/{cinema_name}. The response lists movies, screens, and start times so the assistant can present the next few showings; the user is then handed off to the cinema's booking flow.

GET /api/v1/cinema-detail/search/{cinema_name} to resolve the cinema id, then GET /api/v1/cinema-shedule-showtime/search/{movie_title} for each requested movie.

Editorial dashboard for Ethiopian film journalists

Editors at an Ethiopian entertainment publication pull /api/v1/news/search/{title} and /api/v1/filmography/search/{movie_title} to assemble a single dashboard view of recent coverage and historical filmography for whichever film they are profiling. /api/v1/people/search/{user} fills in the actor side, and /api/v1/company/search/{company_name} surfaces the production studio.

For the article subject, GET /api/v1/news/search/{title}, /api/v1/filmography/search/{movie_title}, and /api/v1/company/search/{company_name} and assemble the merged result for the editor.

AI agent recommending Ethiopian films via Jentic

A recommendation agent answering 'suggest an Ethiopian drama from the last five years' uses Jentic to resolve the right EtMDB endpoints, queries genre and movie searches, and returns a ranked shortlist. Through Jentic, the OAuth2 credentials are held in the vault and the agent only sees a scoped execution token.

Search Jentic for 'find Ethiopian films by genre', execute GET /api/v1/genre/searchall/{movie_genre_type} with 'drama', then for each result fetch /api/v1/movie/search/{movie_title} to enrich and rank the response.

Key Endpoints

27 endpoints — jentic publishes the only available openapi specification for etmdb rest api v1, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/api/v1/movie/search/{movie_title}

Search for a movie by title

GET

/api/v1/movie-cast/search/{movie_title}

Get cast for a movie

GET

/api/v1/people/search/{user}

Search for a person (actor/crew)

GET

/api/v1/cinema-shedule-showtime/search/{movie_title}

Get cinema showtimes for a movie

GET

/api/v1/genre/search/{movie_title}

Look up genre information for a movie

GET

/api/v1/news/search/{title}

Search news or articles by title

GET

/api/v1/movie/search/{movie_title}

Search for a movie by title

GET

/api/v1/movie-cast/search/{movie_title}

Get cast for a movie

GET

/api/v1/people/search/{user}

Search for a person (actor/crew)

GET

/api/v1/cinema-shedule-showtime/search/{movie_title}

Get cinema showtimes for a movie

GET

/api/v1/genre/search/{movie_title}

Look up genre information for a movie

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The EtMDB OAuth2 credentials are stored encrypted in the Jentic vault; agents only ever hold a scoped execution token, so the raw client secret and access token never enter the agent context.

Intent-based discovery

Agents search Jentic with intents like 'find an Ethiopian movie by title' or 'list showtimes for a movie' and Jentic returns the right /search or /searchall operation along with its parameter schema, so the agent does not need to enumerate the 27 endpoints by hand.

Time to first call

Direct integration: 1 day to handle OAuth, the search-vs-searchall pattern, and pagination. Through Jentic: under an hour for the first movie or showtime lookup.

FAQs

Specific to using EtMDB REST API v1 API through Jentic.

Why is there no official OpenAPI spec for EtMDB REST API v1?

EtMDB does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call EtMDB REST API v1 via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the EtMDB REST API use?

The EtMDB REST API uses OAuth 2.0 for access. Through Jentic, the OAuth credentials are stored encrypted in the vault and exchanged for a scoped execution token at call time, so the raw token never enters the agent's prompt context.

What's the difference between /search/ and /searchall/ on EtMDB endpoints?

Most resources expose two variants: /search/{key} returns a narrower match scoped to the supplied key (movie title, cinema name, person name) and /searchall/{param} returns the broader list of matches. Use /searchall when the user gives a partial or category-style input and /search when they give an exact identifier.

What are the rate limits for the EtMDB REST API?

EtMDB does not document an explicit rate-limit policy in this spec. Treat each search as a single request, cache popular results client-side, and back off on any 429 or 5xx response rather than retrying tight loops.

How do I find showtimes for a movie through Jentic?

Search Jentic for 'Ethiopian movie showtimes'. Jentic returns GET /api/v1/cinema-shedule-showtime/search/{movie_title}. Execute it with the movie title and the response includes the cinemas, screens, and start times currently scheduled for that title.

Can I add or update records via this API?

No. Every endpoint in this spec is a GET search; the EtMDB REST v1 surface is read-only. Submitting new movies, cast, or cinema entries is handled through EtMDB's editorial process, not through this API.