# Video Production Plan : Video 1 — Start Here - Certification Roadmap and First API Call

### About this export

| Field | Value |
| --- | --- |
| **content_type** | lesson |
| **platform** | contentstack-academy |
| **source_url** | https://www.contentstack.com/academy/courses/video-production-plan/video-production-plan-video-1-start-here-certification-roadmap-and-first-api-call |
| **course_slug** | video-production-plan |
| **lesson_slug** | video-production-plan-video-1-start-here-certification-roadmap-and-first-api-call |
| **markdown_file_url** | /academy/md/courses/video-production-plan/video-production-plan-video-1-start-here-certification-roadmap-and-first-api-call.md |
| **generated_at** | 2026-08-26T11:17:52.745Z |

> Part of **[Video Production Plan](https://www.contentstack.com/academy/courses/video-production-plan)** on Contentstack Academy. **Academy MD v3** — structured for retrieval; no quiz or assessment keys.

<!-- ai_metadata: {"lesson_id":"16","type":"text","duration_minutes":3,"topics":["Video","Production","Plan","Video","Start","Here"]} -->

#### Lesson text

# Video 1 — Start Here: Certification Roadmap and First API Call

Attribute

Details

Course

0 (Orientation)

Covers

Lessons 0.1.1, 0.1.2, 0.1.3

Priority

Core

Length

10-15 min

Format

Screencast (Contentstack UI + terminal)

Status

Not started

## Why This Video Matters

Gives learners an early win and reduces drop-off at the start of the certification. This is the first thing people see — it needs to be welcoming and confidence-building.

## Outline

1.  Who this certification is for and what the learner is expected to already know
2.  How the curriculum is structured across 7 courses
3.  Quick tour of the documentation ecosystem: developer docs, API references, SDKs (JS, Python, Java, .NET, Ruby, Swift, Dart, Flutter)
4.  Regional API base URLs, Postman collections, GitHub repos
5.  Open the Contentstack dashboard: show a stack, a content type, and an entry
6.  Make a live Content Delivery API call with curl — walk through the request and the JSON response
7.  Repeat the same query with the JavaScript SDK to show the abstraction layer
8.  How to study the rest of the curriculum efficiently

## Key Lines

"This certification is easier if you think of it as one continuous build journey, not a set of disconnected lessons."

"You do not need to memorize every API detail. You need to know where to find the right reference quickly."

"You just fetched your first entry. Everything in this certification builds on this."

## Detailed Talking Points

### 1\. Who this certification is for and what the learner is expected to already know

*   "This certification is for developers who build on top of Contentstack — frontend devs consuming delivery APIs, fullstack devs wiring up preview and webhooks, backend devs integrating into platform architectures."
*   Explain that no prior Contentstack experience is needed, but they should be comfortable with HTML/CSS/JS, REST APIs, JSON, and have used fetch or axios before.
*   Mention the free developer plan — they can sign up and get a stack before starting.
*   Call out what this certification does NOT cover: pricing, sales/marketing features (Personalize, A/B testing), admin tasks (SSO/SAML), or framework-specific tutorials. "This is about Contentstack concepts that apply no matter what framework you use."

### 2\. How the curriculum is structured across 7 courses

*   Walk through each course in one sentence:
    *   Course 1: Foundations — mental model for headless, the 5 building blocks
    *   Course 2: Content Modeling — designing schemas that serve editors AND APIs
    *   Course 3: APIs and Tooling — Delivery API, Management API, REST vs GraphQL, SDK, CLI
    *   Course 4: Preview and Visual Builder — Live Preview, Visual Builder, releases
    *   Course 5: Workflows and Branches — content lifecycle, automation, branching
    *   Course 6: Extensions — when to customize, apps, webhooks
    *   Course 7: Integrations — composable DXP, Launch, Automate, Personalize
*   Emphasize: "Course 1 is mandatory first. After that, you can jump to whatever is most relevant to your current work."
*   Mention the lesson structure: every lesson has a TL;DR, core content, practice activity, common mistakes, and self-check questions. "The self-checks test application, not recall. If you can't answer them, re-read before moving on."

### 3\. Quick tour of the documentation ecosystem

*   Show the developer docs landing page at [contentstack.com/docs/developers/](/docs/developers/) — "Bookmark this. You'll come back to it constantly."
*   Three API surfaces: Content Delivery API (REST), Content Management API (REST), GraphQL Content Delivery API. Briefly explain each in one sentence.
*   "The Delivery API is what your frontend calls in production. The Management API is for automation, migrations, and admin scripts. GraphQL lets you request exactly the fields you need."
*   Mention the SDKs: JavaScript/Node.js (most common), Python, Java, .NET, Ruby, Swift, Dart/Flutter. "You don't need to learn them all. Pick the one for your stack."
*   Point out the SDK docs vs raw API reference distinction: "When an SDK method behaves unexpectedly, check the raw API reference or the SDK source on GitHub. SDK docs sometimes lag behind."

### 4\. Regional API base URLs, Postman collections, GitHub repos

*   Show the region table: NA (cdn.contentstack.io), EU (eu-cdn.contentstack.com), Azure NA (azure-na-cdn.contentstack.com), Azure EU (azure-eu-cdn.contentstack.com), GCP NA (gcp-na-cdn.contentstack.com).
*   "Using the wrong base URL is the number one cause of 'stack not found' errors. It's not an auth problem — it's a region mismatch."
*   Show where to find your stack's region in the dashboard under stack settings.
*   Mention Postman collections — "Import the collection, set up an environment with your api\_key, access\_token, and base\_url, and you can explore every endpoint without writing code."
*   Point to [github.com/contentstack](https://github.com/contentstack) — SDKs, sample apps (Next.js, Gatsby, Nuxt, Angular), CLI tools.
*   Mention npm install -g @contentstack/cli — "We'll use this heavily in Course 3, but know it exists."

### 5\. Open the Contentstack dashboard: show a stack, a content type, and an entry

*   Open the Veda stack in the dashboard. Point out the stack API key in settings.
*   Navigate to Content Types. Open the product content type. "This is both a schema and an editor interface. Every field UID you see here becomes a JSON key in the API response."
*   Point out the field UIDs vs display names — short\_description is the API key, "Short Description" is what editors see.
*   Open a published entry (e.g., a Veda product). Show the title, locale, reference fields, and asset fields.
*   Note the environment and the delivery token scoped to it.

### 6\. Make a live Content Delivery API call with curl

*   Switch to terminal. Run:
    
    curl -s "https://cdn.contentstack.io/v3/content\_types/product/entries?environment=development" \\
      -H "api\_key: YOUR\_KEY" \\
      -H "access\_token: YOUR\_TOKEN" | jq
    
*   Walk through the response: the entries array, field UIDs matching the schema, system fields like uid, locale, timestamps.
*   "Look at one entry. Which fields would a listing page need? Which fields would a detail page need? Which fields stay internal to editors? This is the core shift — you're not building around pages the CMS owns. You're consuming structured JSON."
*   If it fails: "Check region first, then environment, then token scope. Most first-time failures aren't auth issues — they're context mismatches."

### 7\. Repeat the same query with the JavaScript SDK

*   Show the SDK initialization code:
    
    import Contentstack from "@contentstack/delivery-sdk";
    const stack = Contentstack.stack({
      apiKey: process.env.NEXT\_PUBLIC\_CONTENTSTACK\_API\_KEY!,
      deliveryToken: process.env.NEXT\_PUBLIC\_CONTENTSTACK\_DELIVERY\_TOKEN!,
      environment: process.env.NEXT\_PUBLIC\_CONTENTSTACK\_ENVIRONMENT!,
      region: Contentstack.Region.US,
    });
    const result = await stack.contentType("product").entry().query().find();
    console.log(result.entries\[0\]);
    
*   "Same content, same response shape, but now through a developer-friendly library. You don't need to master this yet. The point is seeing that you have two ways in: raw HTTP and SDK."

### 8\. How to study the rest of the curriculum efficiently

*   "Work through Course 1 first. Every later course assumes you understand its vocabulary."
*   "Keep a stack open while you study. Reading about content types is useful; creating one and fetching from it through the API is where it sticks."
*   "Give the self-check questions real effort. If you can't answer them, the next lesson will be harder."
*   "This curriculum is also a reference. When you hit a real-world content modeling decision or API challenge, come back to the relevant lesson."

## Screen: What to Show

1.  Curriculum site — show the course catalog / home page briefly
2.  Developer docs — [contentstack.com/docs/developers/](/docs/developers/) landing page, scroll through the navigation
3.  API reference — open the Content Delivery API reference, show an endpoint page briefly
4.  Region table — either the docs page or a slide showing the 5 regions and their base URLs
5.  Contentstack dashboard — navigate to: Settings → API keys (show stack API key and region), Content Types → open product, Entries → open a Veda product entry
6.  Terminal — run the curl command, pipe to jq, show the JSON response
7.  Code editor — show the SDK initialization code, run it, show console output
8.  Postman (optional) — quickly show a pre-configured Postman collection request

## Veda Scenario Thread

Introduce Veda here for the first time: "Veda is an upscale all-gender jewelry line — four distinct sets inspired by early 2000s pop culture, reinterpreted with modern luxury. Silver, gold, diamonds. This isn't just an example — it's the storefront you'll return to across every course. The same products, categories, and pages will anchor content modeling, API calls, preview, workflows, and integrations." Use a Veda product entry for the curl demo and SDK demo so learners connect to it immediately.

## Transitions

*   Curriculum overview → docs tour: "Before we start building, let me show you where to find answers when you need them."
*   Docs tour → regional URLs: "One thing that trips people up immediately — your API base URL depends on your region."
*   Regional URLs → dashboard walkthrough: "Let's look at the actual stack we'll be working with."
*   Dashboard → curl call: "Now let's prove this works. I'm going to fetch this entry through the API."
*   Curl → SDK: "Same query, but this time through the JavaScript SDK."
*   SDK → study tips: "You just fetched your first entry. Here's how to make the rest of this certification as efficient as possible."
*   Closing → Video 2: "Next, we'll zoom out and build the mental model for headless architecture — what Contentstack is responsible for, what you're responsible for, and why that distinction matters for every decision you'll make."

## Common Mistakes to Call Out

1.  Treating the dashboard as the whole product — "If you only click around the UI and never inspect the API response, Contentstack still feels like a form builder. It's not. It's a structured content platform. The API response is the product."
2.  Using the wrong region or environment — "Many first-time delivery failures aren't authentication failures. They're context mismatches: wrong base URL, wrong environment name, or content that was never published to that environment."
3.  Waiting until Course 3 to touch the APIs — "Don't do this. One successful request now pays off for the rest of the path. The certification gets easier when you connect concepts to a real response early."

## Notes

Use this space for recording notes, script drafts, or post-production feedback.

#### Key takeaways

- Connect **Video Production Plan : Video 1 — Start Here - Certification Roadmap and First API Call** back to your stack configuration before moving to the next module.
- Capture one concrete artifact (screenshot, Postman call, or code snippet) that proves the step works in your environment.
- Re-read the delivery versus management boundary for anything you changed in the entry model.

## Supplement for indexing

### Content summary

Video Production Plan : Video 1 — Start Here - Certification Roadmap and First API Call. Video 1 — Start Here: Certification Roadmap and First API Call Attribute Details Course 0 (Orientation) Covers Lessons 0.1.1, 0.1.2, 0.1.3 Priority Core Length 10-15 min Format Screencast (Contentstack UI + terminal) Status Not started Why This Video Matters Gives learners an early win and reduces drop-off at the start of the certification. This is the first thing people see — it needs to be welcoming and confidence-building. Outline 1. Who this certification is for and what the learner is expected to already know 2. How the curriculum is structured across 7 courses 3. Quick tour of the documentation ecosystem: developer docs, API references, SDKs (JS, Python, Java, .NET, Ruby, Swift, Dart,

### Retrieval tags

- Video
- Production
- Plan
- Start
- Here
- video-production-plan
- lesson 16
- Video Production Plan : Video 1 — Start Here - Certification Roadmap and First API Call
- video-production-plan lesson

### Indexing notes

Index this lesson as a primary chunk tagged with lesson_id "16" and topics: [Video, Production, Plan, Video, Start, Here].
Parent course slug: video-production-plan. Use asset_references URLs as thumbnail hints in search results when present.
Never surface LMS quiz content or assessment answers from this file.

### Asset references

_No image or video thumbnail URLs were extracted._

### External links

| Label | URL |
| --- | --- |
| Contentstack Academy home | `https://www.contentstack.com/academy/` |
| Training instance setup | `https://www.contentstack.com/academy/training-instance` |
| Academy playground (GitHub) | `https://github.com/contentstack/contentstack-academy-playground` |
| Contentstack documentation | `https://www.contentstack.com/docs/` |
| github.com/contentstack | `https://github.com/contentstack` |