Fix inconsistent URL paths in See Also section of Create a REST API page

[Thilina2468]

Purpose

Resolves #11444. The "See Also" section at the bottom of create-a-rest-api.md links to the legacy {{base_path}}/manage-apis/... URL scheme, while the rest of the page uses {{base_path}}/api-design-manage/.... This inconsistency was introduced by PR #10492, which migrated part of the page but left the See Also section on the old scheme.

Goals

Make all 8 "See Also" links consistent with the rest of the page and point at each topic's actual current location.

Approach

Checked en/redirects.yml and the current file tree rather than assuming a simple manage-apis -> api-design-manage swap is correct for every link. That swap is correct for 5 of the 8 links (Endpoints, Life Cycle Management, API Visibility, API Documentation, Custom Properties), but 3 of the pages (API Security, Rate Limiting, API Monetization) were relocated to different top-level sections entirely during a later reorganization:

• API Security -> api-security/runtime/api-authentication/secure-apis-using-oauth2-tokens/
• Rate Limiting -> api-gateway/rate-limiting/understand-rate-limit-enforcement/
• API Monetization -> monitoring/api-monetization/monetizing-an-api/

Each of the 8 replacement targets was confirmed to exist as a real file in the repo before making the change.

User stories

N/A

Release note

Fixed inconsistent/stale links in the "See Also" section of the Create a REST API page.

Documentation

This PR is the documentation fix itself.

Training

N/A

Certification

N/A - no impact on certification exams.

Marketing

N/A

Automation tests

• Unit tests: N/A (documentation content change)
• Integration tests: N/A

Security checks

• Followed secure coding standards: yes
• Ran FindSecurityBugs plugin and verified report: N/A (markdown-only change, no code)
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets: yes

Samples

N/A

Related PRs

Companion PR targeting the 4.7.0 branch (same fix).

Migrations (if applicable)

N/A

Test environment

Verified each of the 8 replacement target files exists in the repository via the GitHub Contents API before applying the change; diffed the file to confirm only the 8 See Also lines changed.

Learning

Cross-referenced en/redirects.yml against the actual file tree to find the true current location of each linked topic, since 3 of the 8 pages had moved to different top-level sections since PR #10492.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

Warning

Review limit reached

@Thilina2468, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 27 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 7b09c82a-0513-40ea-beb5-23436bac48cb

📥 Commits

Reviewing files that changed from the base of the PR and between acd83ed and 6cafbf5.

📒 Files selected for processing (1)

• en/docs/api-design-manage/design/create-api/create-rest-api/create-a-rest-api.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}