I'll create a Next.js API endpoint that returns a Ringba number and sends data to Facebook Conversions API when a caller parameter is provided.

This API endpoint:

1. Accepts GET requests at /api/get-ringba-number
2. Always returns the Ringba number +18776250136

3. If a caller query parameter is provided:

   • Hashes the phone number using SHA256
   • Sends the data to Facebook Conversions API with all required parameters
   • Includes the event name, timestamp, hashed phone, and custom data

To use this endpoint, you'll need to set up environment variables for your Facebook Pixel ID and Access Token:

You can test the endpoint with:

Please make sure to add the following environment variables to your project:

Please make sure to add the following environment variables to your project:

Great! Now that you've added the environment variables to your Vercel project, your API endpoint will be able to use them to authenticate with Facebook's Conversions API.

Testing Your API Endpoint

You can test your API endpoint in a few ways:

Basic Test (No Caller Parameter)

Expected response:

Test with Caller Parameter

Expected response:

This will also trigger the Facebook CAPI event with the hashed phone number.

Verifying Facebook CAPI Events

To verify that events are being sent to Facebook correctly:

1. Go to your Facebook Events Manager
2. Look for "CallLead" events in your event testing tool
3. Check that the hashed phone numbers and custom data are being received correctly

Potential Enhancements

Here are some improvements you might want to consider:

1. Add Rate Limiting: Protect your API from abuse by implementing rate limiting.
2. Improve Error Handling: Add more detailed error responses for different failure scenarios.
3. Add Logging: Implement more comprehensive logging to track API usage and troubleshoot issues.
4. Add Validation: Validate the caller phone number format before processing.

Would you like me to implement any of these enhancements to your API endpoint?