Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Sean Conklin

    (@seanconklin)

    Hi l0c0luke,

    Your web server needs to be able to speak outbound to api.benchmarkemail.com on SSL port 443. If your firewall is blocking this, then you would need to add a rule. Most web servers allow outgoing connections, but you may be in a more secure environment.

    To diagnose your specific issue, I recommend putting a test PHP file in your web root and running it from the command line (php ./test.php) or a web browser to see what’s going on more specifically. The file can contain this sample test run of the listGet command with your API key:

    <?php
    
    // Settings
    $service = 'https://api.benchmarkemail.com/1.0/';
    $api_key = 'PUT-YOUR-API_KEY_HERE';
    $timeout = 30;
    ini_set( 'default_socket_timeout', $timeout );
    
    // Load WP
    require( 'wp-load.php' );
    require( 'wp-includes/class-IXR.php' );
    
    // Try Connection
    $client = new IXR_Client( $service, false, 443, $timeout );
    $args = array( 'listGet', $api_key, '', 1, 100, 'name', 'asc' );
    call_user_func_array( array( $client, 'query' ), $args );
    
    // Output
    print_r( $client->getResponse() );
    
    ?>

    This request suggests that we should have a feature that reports whether it can talk to Benchmark Email API server separately from the individual token authentications. We’ll work on that in an upcoming release.

    Plugin Author Randy Sandberg

    (@randywsandberg)

    Hi l0c0luke, just wondering if you had any luck with Sean’s suggestions for a fix above?

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘api key not valid always’ is closed to new replies.