FedNex logo
v1.0 — Production

FedNex API Services: the backend layer powering auth, content, contact, and AI orchestration.

Versioned REST endpoints with consistent JSON contracts. Built on Laravel 12 with structured validation, rate limiting, and CORS-ready delivery for the entire FedNex platform.

Version

v1

Stable, versioned API contracts.

Endpoints

12+

Across auth, content, contact & AI.

Format

JSON

Structured responses everywhere.

Base URL

All API requests use this base URL:

https://api.fednex.ng/api/v1

Authentication

User identity & access

5 Endpoints
  • POST /api/v1/auth/register
  • POST /api/v1/auth/login
  • POST /api/v1/auth/logout
  • POST /api/v1/auth/forgot-password
  • POST /api/v1/auth/reset-password

Contact

Contact request handling

2 Endpoints
  • POST /api/v1/contact-requests
  • GET /api/v1/contact-requests

Handles form submissions from the main site contact page. GET requires admin authentication.

Content

Platform content delivery

3 Endpoints
  • GET /api/v1/services
  • GET /api/v1/platforms
  • GET /api/v1/training

Read-only endpoints serving structured JSON for the FedNex platform content catalog.

AI Orchestration

AI gateway & routing

2 Endpoints
  • POST /api/v1/ai/chat
  • GET /api/v1/ai/health

Routes chat messages through the API before forwarding to the FastAPI knowledge service at ai.fednex.ng.

Quick Start

Make your first API request

Send a simple health check to verify the API is reachable, then explore the authentication and contact endpoints.

1. Check API Health

curl https://api.fednex.ng/api/v1/health

# Response:
{
  "status": "healthy",
  "version": "1.0.0",
  "timestamp": "2026-03-19T12:00:00Z"
}

2. Submit a Contact Request

curl -X POST https://api.fednex.ng/api/v1/contact-requests \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Jane Doe",
    "email": "jane@example.com",
    "subject": "Integration",
    "message": "Hello FedNex"
  }'

Authentication

Bearer token auth

Protected endpoints require a Bearer token in the Authorization header. Obtain a token by calling the login endpoint with valid credentials.

Authorization: Bearer <your-token>
Token-based session management
CORS-enabled for cross-origin requests
Rate-limited for production safety

Responses

Consistent JSON contracts

Every response follows the same envelope structure for predictable client-side parsing.

{
  "success": true,
  "message": "Request processed",
  "data": { ... },
  "errors": null
}

HTTP Status Codes

200Success
201Created
422Validation Error
401Unauthorized
429Rate Limited
500Server Error

Platform Ecosystem

Connected FedNex applications

The API Services backend connects to and powers all other FedNex platform applications.

Ready to integrate?

Explore the full documentation or reach out to the FedNex team for integration support.