So there was no CF-RAY. That’s what the team needs. 
No. If there was, I would have included it. You can’t use a timestamp? I have nothing else to give you on that front. That’s all that was included in the response from cloudflare.
Are any other API requests from your server working as expected or are all of them failing?
No. It’s only been this one the whole time. Is there any way to enable some more debugging on an API call with the SDK? I can’t seem to find anything about some more logging. I need to see exactly what my headers are that are being sent with the intial request, but I can’t seem to find how to get that information. All I can see is what the SDK says my request headers will be before they send, but not the actual ones being sent.
Bump again. Any answer to my last question about more debugging for the PHP SDK? We’re still being blocked by cloudflare with no reason. I need to see the output for the actual curl request/api call and not what the SDK has set for the headers. Otherwise, I’ll have to remove this feature from our system if we can’t get this resolved. I’m just afraid this is going to happen with another endpoint unless I can figure out why this happened in the first place.
Do you have a ray_id?
It is not returning any ray id. Please reread the ticket, before asking any more questions. Nothing has changed from the beginning of this ticket. Everything is exactly the same.
Can you please answer my question though?
Do you have a video of what’s happening? Is there any additional information in the network calls?
That’s exactly what I’m trying to get. I’ve given you all I can get from the current logging.
Is there any way to enable some more debugging on an API call with the SDK, so I can see the headers that are being sent and not the headers that the SDK has set?